"annotate" => bin-clash about annotate_models HOT 7 CLOSED

That's not good but I don't know what I can do about that. Any suggestion?

from annotate_models.

hah, maybe have an additional bin that do the same thing, named "annote-rails" or something like that. That's what I did before, just don't forget adding the new bin command to the Gem spec - I forgot that plenty of times in vain. =)

from annotate_models.

I solved this issue on my fork.

http://github.com/masa-iwasaki/annotate_models/commit/27a0fe964e306a83a61aca886d505bea5150cb6c

from annotate_models.

What I'll do is to create 2 executables, "annotate" and "annotate-rails". People with the gdlib2 will use annotate-rails while others can still use annotate.

from annotate_models.

How about making this gem work as a rake command rather than a system binary? Then you can have

rake annotate:all
rake annotate:routes
etc

from annotate_models.

+1 to ari's suggestion. This should create a rake task rather than make a binary. Or, if you want maximum flexibility, have it do both so that those of us with gdlib or ImageMagick installed can still run annotate without messing with $PATH.

from annotate_models.

+1 for making it a rake task! If you do it, can you please follow thinking sphinx style so that it's easy to use it as a gem: http://github.com/freelancing-god/thinking-sphinx/blob/master/tasks/rails.rake

from annotate_models.