On Thu, Mar 10, 2011 at 05:14:50PM -0800, Jeremy Evans wrote: > Simple version bump for unicorn, changelog here: > http://unicorn.bogomips.org/NEWS.html > > One port change is that the man pages for unicorn and unicorn_rails > are now installed into the standard man page directory. This > will fix the issue where whatis.db is created instead the gem directory > leading to errors when the package is upgraded or deleted. > > Unfortunately, this will cause a conflict between the rbx-unicorn and > ruby-unicorn packages where there was none before, since they will both > attempt install the same man page (the ruby19-unicorn package doesn't > conflict with either, since it uses the same 19 suffix the bin files > use). This could be handled in one of the following ways: > > 1) Use the current diff, which lacks explicit conflict marking. The pkg > tools will still note the conflict when an install is attempted.
Gross. > 2) Add explicit conflict marking, using PFRAG.rbx and > PFRAG.no-rbx,no-ruby19 (or whatever the necessary filename is). > Results in a nicer error message if you attempt to install conflicting > packages. Gah, we're only talking about a _manpage_, not a zomg-super-important file :) > 3) Name the rbx-unicorn package man page differently, so it no longer > conflicts. However, it will then no longer match the binary name. The > rbx version is generally invoked as rbx -S unicorn, unless the user > specifically modifies their PATH to add the rubinius bin directory > before the standard bin directory. I think that's the saner approach.. after all, binaries/files are already renamed depending on the flavor to avoid such conflicts. > Note that neither the ruby19 or rbx FLAVOR is built by default. I would > like to build the ruby19 FLAVOR by default, though. Sure sure. landry
