Stop using mattr_accessor, fixes up to the postgres :limit issue.

[shekibobo]

Fixes travis builds up to the postgres limit issue #416 and #409.

As an added bonus, I also added an in stall generator which creates an acts_as_taggable_on.rb initializer to set up configuration options.

[shekibobo]

Any idea why the spec/schema.rb sets integers with :limit => 11? That's breaking the specs in Postgres on Travis (though those pass just fine on my system using wwtd because "No integer type has byte size 11." Any thoughts on this?

[bf4]

Can you rebase against master and force push?

[bf4]

So, the mattr_accessor issue is fixed in master, now, but the other changes are interesting. Will review.

[fguillen]

I'm using v2.4.1 and I having the error:

acts-as-taggable-on-2.4.1/lib/acts-as-taggable-on.rb:10:in `<module:ActsAsTaggableOn>': undefined method `mattr_accessor' for ActsAsTaggableOn:Module (NoMethodError)

I suppose is related to this thread.

How can I define my "acts-as-taggable-on" dependency in a .gemspec file to use a version with this issue fixed?

I think the fixed version must be in "rubygems" in order to be able to be included in a .gemspec file :/. I think I can't point to a git repo in a .gemspec file.

[bf4]

@fguillen Yes, only bundler can install from source. Until someone with push access can release a new version of the gem, your options are to fork and release a temporary name-spaced build of your own, or to do so with your own gemserver.

[fguillen]

Thanks for the support @bf4 my workaround has been to add this require:

require "active_support/core_ext/module"

Before:

require "acts-as-taggable-on"

[bf4]

@fguillen that works

[bf4]

This PR should be renamed to 'Add configuration initializer generator', no?