-r2 adds in gift-fasttrack, which is a very nice addition. However, this has one problem. During the configure stage of gift-fasttrack, it checks for libgift, and if this is the first time one is emerging gift, this will fail. I suppouse one possible solution is to depend on an earlier version of gift, or to move gift-fasttrack out into an independent ebuild that depends on gift-cvs. Reproducible: Always Steps to Reproduce: 1.emerge -C gift-cvs 2.emerge /usr/portage/net-p2p/gift-cvs/gift-cvs-0.10.0-r2.ebuild Actual Results: Configure of gift-fasttrack is not able to find libgift. Expected Results: A succesful build of gift-cvs
I also get these problems, and have for quite a while. Any progress possible?
gift-fasttrack requires giFT to be installed at build time. A dirty workaround would be creating a modified version of libgift.pc and adding it's directory to PKG_CONFIG_PATH in the ebuild to lead configure (of gift-fasttrack) to the current location of the library (in my case /var/tmp/portage/gift-cvs-0.10.0-r2/work/giFT/lib). Or one could create a modified version of gift-fasttrack's configure script. I don't think it makes much sense to include gift-fasttrack in the ebuild, so I have created gift-cvs-0.10.0-r3.ebuild and gift-fasttrack-cvs-0.8.0.ebuild, both basing on the gift-cvs-0.10.0-r2.ebuild. By the way, sourceforge refuses most cvs logins, I had to rerun emerge multiple times until the login was successful. cjay
Created attachment 13933 [details] ebuild for separate gift fasttrack plugin
Created attachment 13934 [details] new gift ebuild without fasttrack plugin
I just tested these separate ebuilds and they seem to work nicely. I think that this separation should be integrated into portage.
did this already a while ago...
