Suggestion to also install tools/build/* from boost. While trying to get PythonMagick to build from outside of the boost tree (bug #35279) I found I needed python.jam amongst others to be installed. (See http://www.python.org/cgi-bin/moinmoin/boost_2epython_2fBuildingExtensions) This update to the boost ebuild adds just one instruction: find tools/build -maxdepth 1 \ -exec install -D -m0644 {} ${D}/usr/include/boost/{} \; to install files (but no subdirs) from tools/build into /usr/include/boost/tools/build. This of course does include files for other architectures (716KB in total) and may not be the best location. Chris
Created attachment 22130 [details] boost-1.30.2-r1 ebuild
george, you seem to be the maintainer of this package. can you please take a look at this? and while you're at it, maybe add a metadata.xml? thanks
Hi Chris. Thanks for the suggestion, but unfortnately it does not work :). The real reason is I thinkf that I had to move to current version in cvs, as this release does not work with python 2.3 (see #35268 for more details). Instead I did some recoursive copying.. Oh, /usr/include/boost/tools/build is definitely bad location, as these are tools and /usr/include is not supposed to contain such stuff. Seing that these tools are comprised of bunch of .jam ans html/css files I am not sure /usr/lib/boost is the proper place either (they are not relly "regular" binaries). So I ended up with /usr/share/{PN} for now. Please do check this and let me know if there is a problem with that. Alastair: >george, you seem to be the maintainer of this package. can you please take a >look at this? Ok, doing this :) >and while you're at it, maybe add a metadata.xml? but not this. See my email to -dev for reasons. I just temporarily picked this one up. I would rather see C/C++/lib dev responsible for it eventually. George
Created attachment 22489 [details] boost-1.30.2-r1 ebuild (second attempt) George I tried boost-1.31.0_alpha1, changed my boost-build.jam to: boost-build /usr/share/boost/v1 and in set BOOST_BUILD_PATH=/usr/share/boost/v1 and got: Jamfile:1: in load-jamfiles *** argument error * rule project-root ( ) * called with: ( PythonMagick ) * extra argument PythonMagick /usr/share/boost/v1/allyourbase.jam:1206:see definition of rule 'project-root' being called /usr/share/boost/v1/bootstrap.jam:15: in boost-build /var/tmp/portage/pythonmagick-0.5/work/PythonMagick/boost-build.jam:3: in module scope Does this make any sense? I think It's difficult enough trying to figure out what to do with the released version of boost from the available documentation - using the CVS without any docs is another challenge altogether! While we try to get this working can 1.30 be kept alive until 1.31 is formally released? I have updated the boost-1.30.2-r1 ebuild to put tools/build under /usr/share/boost and added a DEPEND line to block python 2.3 (can you have two depend lines for the same package?). Chris
Sorry for the silence in this bug, there was a lot of discussion in other one, but all is good now :). Release is out and in stable, closing the bug..
