capistrano 2.0.0 was released on 2007/07/21.
I create an ebuild for this new upstream version
Created attachment 126824 [details] The ebuild of capistrano 2.0.0 The new version for install capistrano 2.0.0
Given that capistrano 1.x and capistrano 2.x are not fully compatible with each other we should probably put each version into it's own slot, and use an eselect module to allow people to switch around. This mirrors advice from upstream to keep both gems installed if needed. I'd like to do this before letting 2.0 hit the tree.
There are now updated ebuilds and an eselect module in my git overlay at http://moving-innovations.com/overlay/ I'd like to get some feedback on them before putting them in the tree, so some testing would be appreciated.
Works swell for me in my tests.
Here is the summation of some things graaff and I discussed in #gentoo-ruby: The cap script that both slots install is actually identical. It uses some magic so you do 'cap _1.4.1 sometask' to use the 1.4.1 version. So, instead of an eselect module, we'd need a separate package that just has /usr/bin/cap, and then the capistrano ebuilds can depend on that. It gets a little tricky to figure out the proper dependencies and blockers, to avoid file-collisions and to make a sane upgrade path.
This sounds like a clunky solution that may be more work that we would want. Hmm. I suppose we could just write out cap-1.4.1 and cap-2.0.0 to /usr/bin in the ebuild, like with eselect, and then create a symlink from /usr/bin/cap to whatever version we're installing in post?
Added to portage earlier this evening.
