[Bug 210644] www/rubygem-redmine_acts_as_taggable_on: Update to 1.1.0

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210644

Torsten Zuehlsdorff <tz at freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tz at freebsd.org

--- Comment #1 from Torsten Zuehlsdorff <tz at freebsd.org> ---
Hello Mark,

since i wrote the update of redmine to 3.x i grep this issue ;)

I'm not sure if i really got your problem. Your link to a "maintained codebase"
points to https://github.com/aledbevi/redmine_acts_as_taggable_on, but this is
a 404 page. Also the user "aledbevi" did not exist on github (or is now
deleted). Your patch changes it to
https://github.com/alexbevi/redmine_acts_as_taggable_on, which works.

The master is https://github.com/hdgarrood/redmine_acts_as_taggable_on, but
there is the latest release 1.1.0.

But when reading your committ-log you want to force the usage of rails4. You
did this by switching from www/rubygem-acts-as-taggable-on to
www/rubygem-acts-as-taggable-on3. But this are different versions.
If www/rubygem-redmine_acts_as_taggable_on relies on the old version of
rubygem-acts-as-taggable-on this will cause problems.

So in conclusion: you forked the project and patch it to work with the new
version of act-as-taggable-on to avoid the usage of rails 3? Am i correct?

If this is the case there is good news for you: this is not needed. I'm
currently in progress to remove Rails 3 from the portstree. It is just possible
to patch www/rubygem-acts-as-taggable-on to use rails 4. I have a patch for
this (with a bunch of others). Are you interested in testing?

Greetings,
Torsten

-- 
You are receiving this mail because:
You are the assignee for the bug.