Rev bump needed on dev-util/bzr to 0.18 [Note I don't care about bzrtools, just bzr] Cheers! AfC
Manually copying brz-0.17.ebuild to bzr-0.18.ebuild in my /usr/local/portage overlay worked no problem. AfC
*** Bug 190609 has been marked as a duplicate of this bug. ***
Created attachment 129523 [details, diff] Simpler way to deal with the man dir issue Existing 0.16 ebuild works for 0.90 so long as you drop out the files/ patch and just move the man dir manually. AfC
FYI, I've incorporated the patch into my bzr-related overlay <https://launchpad.net/bzr-gentoo-overlay>. Thanks!
Someone packaging for another distro just reported in #bzr that --install-data /usr/share as an argument to setup.py seems to solve the mandir problem; that would make both the hack in the current .ebuild and the workaround in my submitted one-liner patch unnecessary. AfC
I could really use this ebuild! Please revbump this when time permits. Thank you, ebuild team! :)
Huh. bzr-0.90 uses pyrex to build some of its index code through C to native for performance improvements. The ebuild should thus depend on dev-python/pyrex AfC
(In reply to comment #5) > Someone packaging for another distro just reported in #bzr that > > --install-data /usr/share > > as an argument to setup.py seems to solve the mandir problem; that would make > both the hack in the current .ebuild and the workaround in my submitted > one-liner patch unnecessary. I've incorporated this fix into my repository. Thanks! (In reply to comment #7) > Huh. bzr-0.90 uses pyrex to build some of its index code through C to native > for performance improvements. The ebuild should thus depend on > dev-python/pyrex Well, I guess it depends on whether we need to patch the pyrex files; the tarballs come with the generated C files, so pyrex shouldn't be run unless one of those files get modified. The Bazaar developers wrote their install script so that pyrex wouldn't be needed unless they were building from a development branch. Then again, I don't know what Gentoo policy is on this one. I'll change my ebuild accordingly.
bzr-0.90 is in CVS, thanks for reporting ;). About the pyrex issue, we usually leave that to upstream unless the generated code has problems, i.e. generated with an old pyrex version etc.
