dev-libs/boost-1.42.0_beta1 is in my overlay [1]. Final release is scheduled for 2010-02-01. Changes concerning the ebuild: * expat dependency / use flag is gone (it's no longer required) * static use flag: if disabled, only the dynamic variant is installed (if available). I expect some packages to fail. The headers of Property Map in the top level include directory were deprecated with 1.40 and are now removed. Affected packages need bugs filed. Feel free to test. [1] http://github.com/few/few-s-gentoo-overlay
1.42 is out. Ebuild is in the overlay.
I would like to test your overlay, but have not found a way to access it (other than by web) How can I add your github overlay to the overlay list used by layman? What is the url? git://github.com/few/few-s-gentoo-overlay?
(In reply to comment #2) > I would like to test your overlay, but have not found a way to access it (other > than by web) > > How can I add your github overlay to the overlay list used by layman? What is > the url? git://github.com/few/few-s-gentoo-overlay? > Put the following lines in some file. Then add the file to /etc/layman/layman.cfg under "overlays". <?xml version="1.0" encoding="UTF-8"?> <layman> <overlay contact="SebastianLuther@gmx.de" name="few" src="git://github.com/few/few-s-gentoo-overlay.git" status="unofficial" type="git"> <description>few's overlay</description> </overlay> </layman>
*** Bug 306901 has been marked as a duplicate of this bug. ***
I really such at searching for dupes it seems. Anyway - 'static' USE flag is wrong - should be 'static-libs'. 'static' USE flag semantics is "build statically linked executables". Obviously - as boost is library/c++ templates collection - you're after "build and install static libraries (static archives) additionally to shared libraries" - that's what 'static-libs' USE flag is for. Btw, I suppose it's not possible/safe/compatible to have multi-thread variant optional as well?
well, with use flag deps we could give IUSE=threads another try. Altough I have the impression that a) only a small part of upstream devs know the difference and b) only a handful of ebuild devs know whether or not they have to depend on boost[threads] resulting in most ebuilds to depend on boost[threads] anyway.
(In reply to comment #5) > Anyway - 'static' USE flag is wrong - should be 'static-libs'. Thanks, I'll fix that. > Btw, I suppose it's not possible/safe/compatible to have multi-thread variant > optional as well? Possible yes, but more than the half of all ebuilds using boost fail without the mt variant and it doesn't lower the compile time that much. It's not worth the hassle.
1.42.0 is now in the tree.