# HG changeset patch
# User Binki <ohnobinki@ohnopublishing.net>
# Date 2009-12-06 01:16:26
# Node ID f2b9d04d0d05c1513604be8cab9886b3e44f183a
# Parent  b9875e4317487339b4b0f0de19af231d9df5ff6b

dev-util/boost-build: Initial import from Gentoo's Portage

diff --git a/dev-util/boost-build/ChangeLog b/dev-util/boost-build/ChangeLog
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/ChangeLog
@@ -0,0 +1,187 @@
+# ChangeLog for dev-util/boost-build
+# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/ChangeLog,v 1.45 2009/12/02 15:26:48 djc Exp $
+
+  02 Dec 2009; Dirkjan Ochtman <djc@gentoo.org> metadata.xml:
+  Add maintainer-by-proxy.
+
+*boost-build-1.41.0 (02 Dec 2009)
+
+  02 Dec 2009; Dirkjan Ochtman <djc@gentoo.org>
+  +files/boost-1.41-fix-mpich2-detection.patch, +boost-build-1.41.0.ebuild:
+  Version bump to boost-build-1.41.0.
+
+  25 Oct 2009; Markus Meier <maekke@gentoo.org>
+  boost-build-1.35.0-r2.ebuild:
+  amd64/x86 stable, bug #284686
+
+  24 Oct 2009; nixnut <nixnut@gentoo.org> boost-build-1.35.0-r2.ebuild:
+  ppc stable #284686
+
+  24 Oct 2009; Mike Frysinger <vapier@gentoo.org>
+  boost-build-1.35.0-r2.ebuild, boost-build-1.36.0.ebuild,
+  boost-build-1.37.0.ebuild, boost-build-1.39.0.ebuild,
+  boost-build-1.40.0.ebuild:
+  Add missing `die` check to tarball unpack.
+
+  23 Oct 2009; Jeroen Roovers <jer@gentoo.org> boost-build-1.35.0-r2.ebuild:
+  Stable for HPPA (bug #288723).
+
+*boost-build-1.40.0 (21 Oct 2009)
+
+  21 Oct 2009; Dirkjan Ochtman <djc@gentoo.org> +boost-build-1.40.0.ebuild,
+  metadata.xml:
+  Version bump to 1.40 (add myself to maintainers).
+
+*boost-build-1.39.0 (16 Jul 2009)
+
+  16 Jul 2009; Tiziano Müller <dev-zero@gentoo.org>
+  +boost-build-1.39.0.ebuild:
+  Version bump (bug #261400).
+
+  15 May 2009; Raúl Porcel <armin76@gentoo.org>
+  boost-build-1.35.0-r1.ebuild:
+  arm/s390/sh stable wrt #245192
+
+  14 Apr 2009; Brent Baude <ranger@gentoo.org> boost-build-1.35.0-r1.ebuild:
+  Marking boost-build-1.35.0-r1 ppc64 for bug 245192
+
+  04 Apr 2009; Raúl Porcel <armin76@gentoo.org>
+  boost-build-1.35.0-r1.ebuild:
+  ia64 stable wrt #245192
+
+  04 Apr 2009; Markus Meier <maekke@gentoo.org>
+  boost-build-1.35.0-r1.ebuild:
+  x86 stable, bug #245192
+
+  02 Apr 2009; Friedrich Oslage <bluebird@gentoo.org>
+  boost-build-1.35.0-r1.ebuild:
+  Stable on sparc, bug #245192
+
+  01 Apr 2009; Joseph Jezak <josejx@gentoo.org>
+  boost-build-1.35.0-r1.ebuild:
+  Marked ppc stable for bug #245192.
+
+  29 Mar 2009; Thomas Anderson <gentoofan23@gentoo.org>
+  boost-build-1.35.0-r1.ebuild:
+  stable amd64, bug 245192
+
+  24 Mar 2009; Ryan Hill <dirtyepic@gentoo.org> boost-build-1.34.1.ebuild,
+  boost-build-1.35.0-r1.ebuild, boost-build-1.35.0-r2.ebuild,
+  boost-build-1.36.0.ebuild, boost-build-1.37.0.ebuild:
+  Fix homepage. Bug #234246.
+
+  07 Feb 2009; Tobias Klausmann <klausman@gentoo.org>
+  boost-build-1.35.0-r1.ebuild:
+  Stable on alpha, bug #245192
+
+*boost-build-1.37.0 (16 Dec 2008)
+*boost-build-1.36.0 (16 Dec 2008)
+*boost-build-1.35.0-r2 (16 Dec 2008)
+
+  16 Dec 2008; Tiziano Müller <dev-zero@gentoo.org>
+  +boost-build-1.35.0-r2.ebuild, +boost-build-1.36.0.ebuild,
+  +boost-build-1.37.0.ebuild:
+  Version bump. Still p.masked since the new versions are slottable.
+
+*boost-build-1.35.0-r1 (05 Jun 2008)
+
+  05 Jun 2008; Tiziano Müller <dev-zero@gentoo.org>
+  +files/1.35.0-fix_broken_icu_build.patch, -boost-build-1.35.0.ebuild,
+  +boost-build-1.35.0-r1.ebuild:
+  Fixed ICU compilation bug
+
+  05 May 2008; Jeroen Roovers <jer@gentoo.org> boost-build-1.34.1.ebuild,
+  boost-build-1.35.0.ebuild:
+  Remove unneeded quotation marks (bug #210029, comment #30).
+
+*boost-build-1.35.0 (24 Apr 2008)
+
+  24 Apr 2008; Tiziano Müller <dev-zero@gentoo.org>
+  +boost-build-1.35.0.ebuild:
+  Version bump (bug #216037)
+
+  15 Mar 2008; Tiziano Müller <dev-zero@gentoo.org>
+  boost-build-1.34.1.ebuild:
+  Fixed typo in description.
+
+  14 Feb 2008; Mark Loeser <halcy0n@gentoo.org> boost-build-1.34.1.ebuild:
+  Fix bug #210029; thanks to Daniel Pielmeier <daniel.pielmeier AT googlemail
+  DOT com>
+
+  13 Feb 2008; Tiziano Müller <dev-zero@gentoo.org>
+  boost-build-1.34.1.ebuild:
+  Added python USE-flag. Adding LDFLAGS to LIBS to fix bug #209794 (see ebuild
+  for more info).
+
+  05 Feb 2008; Samuli Suominen <drac@gentoo.org> boost-build-1.34.1.ebuild:
+  amd64 stable wrt security #205955
+
+  26 Jan 2008; Tobias Scherbaum <dertobi123@gentoo.org>
+  boost-build-1.34.1.ebuild:
+  ppc stable, bug #205955
+
+  26 Jan 2008; Jeroen Roovers <jer@gentoo.org> boost-build-1.34.1.ebuild:
+  Stable for HPPA (bug #205955).
+
+  25 Jan 2008; Markus Rothe <corsair@gentoo.org> boost-build-1.34.1.ebuild:
+  Stable on ppc64; bug #205955
+
+  25 Jan 2008; Raúl Porcel <armin76@gentoo.org> boost-build-1.34.1.ebuild:
+  alpha/ia64/sparc stable wrt security #205955
+
+  24 Jan 2008; Christian Faulhammer <opfer@gentoo.org>
+  boost-build-1.34.1.ebuild:
+  stable x86, security bug 205955
+
+  20 Jan 2008; Ryan Hill <dirtyepic@gentoo.org> Manifest:
+  Fix Manifest.
+
+  24 Dec 2007; Tiziano Müller <dev-zero@gentoo.org>
+  -boost-build-1.34.0.ebuild:
+  Dropped old version.
+
+  26 Sep 2007; Tiziano Müller <dev-zero@gentoo.org>
+  boost-build-1.34.1.ebuild:
+  Marked ~arm and ~sh for bug #182196
+
+*boost-build-1.34.1 (29 Jul 2007)
+
+  29 Jul 2007; Tiziano Müller <dev-zero@gentoo.org>
+  +boost-build-1.34.1.ebuild:
+  Version bump (bug #186811)
+
+  23 Jun 2007; Joshua Kinard <kumba@gentoo.org> boost-build-1.34.0.ebuild:
+  Marked unstable on mips, per #182196.
+
+  20 Jun 2007; Joseph Jezak <josejx@gentoo.org> boost-build-1.34.0.ebuild:
+  Marked ~ppc for bug #182196.
+
+  18 Jun 2007; Raúl Porcel <armin76@gentoo.org> boost-build-1.34.0.ebuild:
+  Add ~alpha/~ia64 wrt #182196
+
+  18 Jun 2007; Markus Rothe <corsair@gentoo.org> boost-build-1.34.0.ebuild:
+  Added ~ppc64; bug #182196
+
+  18 Jun 2007; Jeroen Roovers <jer@gentoo.org> boost-build-1.34.0.ebuild:
+  Marked ~hppa (bug #182196).
+
+  16 Jun 2007; Ferris McCormick <fmccor@gentoo.org>
+  boost-build-1.34.0.ebuild:
+  Add ~sparc keyword --- part of Bug #182196 --- installs as expected.
+
+  10 Jun 2007; Ryan Hill <dirtyepic@gentoo.org> boost-build-1.34.0.ebuild:
+  Boost building boost-build with GCC 4.2, bug #181139.
+
+*boost-build-1.34.0 (03 Jun 2007)
+
+  03 Jun 2007; Tiziano Müller <dev-zero@gentoo.org>
+  -boost-build-1.34_pre20061214.ebuild, +boost-build-1.34.0.ebuild:
+  Version bump.
+
+*boost-build-1.34_pre20061214 (18 Dec 2006)
+
+  18 Dec 2006; Tiziano Müller <dev-zero@gentoo.org> +metadata.xml,
+  +boost-build-1.34_pre20061214.ebuild:
+  Initial commit.
+
diff --git a/dev-util/boost-build/Manifest b/dev-util/boost-build/Manifest
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/Manifest
@@ -0,0 +1,19 @@
+AUX 1.35.0-fix_broken_icu_build.patch 1752 RMD160 0e7ee05c17d76e29abff915e84181361e4095b89 SHA1 273de1fa957091bf3c0d041f54aec9797810f3cf SHA256 71d858236c47b835947d996d3caf0a1de96ace267140d52dd09594db3a96729d
+AUX boost-1.41-fix-mpich2-detection.patch 1378 RMD160 fd81c6a03dd8bf2d6afdaf3fa4957ee0ff1f6e10 SHA1 bbe5ba6fb554ab89e5fa4649f8a44ad7cd1dfa80 SHA256 8e1adadb1345ff045930bbd1c6d9d6e4b06462de2939021bf9e3a3fe1c9d6100
+DIST boost_1_34_1.tar.bz2 12986931 RMD160 303327ff852bc19dd7a94657fdef3c56f5882e06 SHA1 b771271d5cbd3bdb0f119dd66dfd36bad7a66866 SHA256 0f866c75b025a4f1340117a106595cc0675f48ba1e5a9b5c221ec7f19e96ec4c
+DIST boost_1_35_0.tar.bz2 23416747 RMD160 89dc46b7841cd288b5fb6f4b9a1ac7309786dc14 SHA1 80d1fe7b0c45541e2af7628295b18f2af996de16 SHA256 f8bf7368a22ccf2e2cf77048ab2129744be4c03f8488c76ad31c0aa229b280da
+DIST boost_1_36_0.tar.bz2 28839275 RMD160 0ac38ee3c355c22fd5534bc806bf516890e5182d SHA1 b8f0f5d90b260aff995ef38fad4eee5e73d00810 SHA256 9a4a0cfbbd227c20a13519a2c41f2e707dc0d89e518a3c7bfcd381f7b7fbcdef
+DIST boost_1_37_0.tar.bz2 29435646 RMD160 3c4cf7eb97a8fb126e564ba529ed9edec8765185 SHA1 c0d0cf9ad8d954507824aed51a3e93e6a9da1d99 SHA256 d52ef49f70b1b9addc4e0d1a3a2a1966227f0d173c3301bac3e6d399eeac5472
+DIST boost_1_39_0.tar.bz2 29408537 RMD160 4962256b48fa8563bf373b8bed97cc8655206a51 SHA1 6af42f74ab24ccc51589a025593bad298c8adde8 SHA256 44785eae8c6cce61a29a8a51f9b737e57b34d66baa7c0bcd4af188832b8018fd
+DIST boost_1_40_0.tar.bz2 32068759 RMD160 dabcc7442b73048095aa3037917ea0713782781f SHA1 9dbaa06ce1d99ce310011c2eaf816ecb003b3096 SHA256 36cf4a239b587067a4923fdf6e290525a14c3af29829524fa73f3dec6841530c
+DIST boost_1_41_0.tar.bz2 33348161 RMD160 a604ef5a6f6f5bf50be59206c8534258ab431aea SHA1 31134e28866b90c39ca4a903c263e036bb25550c SHA256 1ef94e6749eaf13318284b4f629be063544c7015b45e38113b975ac1945cc726
+EBUILD boost-build-1.34.1.ebuild 2411 RMD160 7be71b552599041c34edf127d3f5dcb1b9095704 SHA1 bbc8007bcdd882b373ce72e8f4aa79c51c6d588d SHA256 5b80a98674bf5e7a192910b49e2c24429a56021b5b0e7d210ad936849724a491
+EBUILD boost-build-1.35.0-r1.ebuild 2739 RMD160 94abd6846df6125a847a5e179be257df8f5a7828 SHA1 d58da24de89cd40f31ab7d7d6874e1e96a7bc221 SHA256 1b83e4c6744f3e9c2d1c90aa71b64c2c31a86f78e8b6bfdac6c1b7d34931e6ba
+EBUILD boost-build-1.35.0-r2.ebuild 3098 RMD160 8631871399c9d458d0a8ec1022b5c527b88bfdd9 SHA1 e9cab38a2cb6fe488e8be8bca5cb4441bc5601e6 SHA256 f73affff86e7c8419d00c783865d3e142357fa0f746816de0ba1dec8bea2c3cd
+EBUILD boost-build-1.36.0.ebuild 3074 RMD160 8d1842fef67b1d548e17c83f71b5e87dc816d203 SHA1 c0559c90f553041e8385918ae9e3bf882ddade6f SHA256 a5905e5e8b3bae14348d1dae2aff3ad9fe806c2803a4eb8767fbffa12ad4b8d9
+EBUILD boost-build-1.37.0.ebuild 3074 RMD160 b820f5d6fb4900415d4b2b9a0d0210259ca4ce43 SHA1 549cc53a910e3a136f4b89cbe160ef2a22b5d12c SHA256 897dada82140ab90f2e070e47eda9218212a6a42bec647f6dd79804dfeeeb1af
+EBUILD boost-build-1.39.0.ebuild 3088 RMD160 1c975b1dfc2c74d2a8fb062b3ea7acd38cc0c47e SHA1 31241c77120276c0b1165f406969956f5f92ed1d SHA256 ddb92e4024ad643380e69b8955faffa2a7717eaf3ca708c7b3525bd7dfd6c9ce
+EBUILD boost-build-1.40.0.ebuild 3088 RMD160 0d56aa2c43dacf5b651fe8c5c9200e7e333752e4 SHA1 136e05dbc06ec5577c9351203597724b53fe523d SHA256 27238ea11d03915c5cfe118cbcd14cae5081ebea2e2cede4d8c344e8dffc8ff0
+EBUILD boost-build-1.41.0.ebuild 3280 RMD160 c1c851b85150f9d308069ff934062c54f4586cc4 SHA1 4b00d041fffed5b3a739e1f018a3ebfb871a13e3 SHA256 645b0d4a02575b6bdd219d17e4f8b6b3318edb766ca0e743854859889d16e08d
+MISC ChangeLog 6162 RMD160 7ec63c039e66c22c4314fa2e79c59c33e822aba8 SHA1 0f6297b323fc5d970f2a790a08f3f3fdbfdb711f SHA256 6882edef976f25789575f09d65e4010dfe92a559063b8961e0d27ae275a81b7d
+MISC metadata.xml 463 RMD160 34d5c35b8b90d95c575275d7c70b9de878a0f041 SHA1 e0a4a54df29c5c50dc32f0c98388d7d24001b522 SHA256 8c386e08bcf70f91461693c7a38cb08fed8232dd0775886be0b801bf6bdb4191
diff --git a/dev-util/boost-build/boost-build-1.34.1.ebuild b/dev-util/boost-build/boost-build-1.34.1.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.34.1.ebuild
@@ -0,0 +1,79 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.34.1.ebuild,v 1.16 2009/03/24 04:34:42 dirtyepic Exp $
+
+inherit flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+
+LICENSE="Boost-1.0"
+SLOT="0"
+KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86"
+IUSE="python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	python? ( dev-lang/python )"
+RDEPEND=""
+
+S=${WORKDIR}/boost_${MY_PV}/tools
+
+src_unpack() {
+	unpack ${A}
+
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i \
+		-e 's/-s\b//' \
+		build.jam || die "sed failed"
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(feature optimization : off speed space\)/\1 none/' \
+		-e 's/\(feature debug-symbols : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	dobin jam/src/bin.*/bjam || die
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+}
diff --git a/dev-util/boost-build/boost-build-1.35.0-r1.ebuild b/dev-util/boost-build/boost-build-1.35.0-r1.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.35.0-r1.ebuild
@@ -0,0 +1,94 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.35.0-r1.ebuild,v 1.10 2009/05/15 14:48:21 armin76 Exp $
+
+inherit flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+LICENSE="Boost-1.0"
+SLOT="0"
+KEYWORDS="alpha amd64 arm ~hppa ia64 ~mips ppc ppc64 s390 sh sparc x86"
+IUSE="examples python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	python? ( dev-lang/python )"
+RDEPEND="${DEPEND}"
+
+S=${WORKDIR}/boost_${MY_PV}/tools
+
+src_unpack() {
+	unpack ${A}
+	cd "${S}"
+
+	epatch "${FILESDIR}/${PV}-fix_broken_icu_build.patch"
+
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i \
+		-e 's/-s\b//' \
+		build.jam || die "sed failed"
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(off speed space\)/\1 none/' \
+		-e 's/\(debug-symbols      : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	dobin jam/src/bin.*/bjam
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+
+	dodoc doc/userman.pdf changes.txt hacking.txt release_procedure.txt \
+		notes/build_dir_option.txt notes/relative_source_paths.txt
+
+	if use examples ; then
+		insinto /usr/share/doc/${PF}
+		doins -r examples
+	fi
+}
+
+src_test() {
+	cd jam/test
+	./test.sh || die "tests failed"
+}
diff --git a/dev-util/boost-build/boost-build-1.35.0-r2.ebuild b/dev-util/boost-build/boost-build-1.35.0-r2.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.35.0-r2.ebuild
@@ -0,0 +1,105 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.35.0-r2.ebuild,v 1.8 2009/10/25 11:57:14 maekke Exp $
+
+EAPI="2"
+
+inherit eutils flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))"
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+LICENSE="Boost-1.0"
+SLOT="0"
+KEYWORDS="~alpha amd64 ~arm hppa ~ia64 ~mips ppc ~ppc64 ~s390 ~sh ~sparc x86"
+IUSE="examples python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	python? ( dev-lang/python )"
+RDEPEND="${DEPEND}"
+
+S="${WORKDIR}/boost_${MY_PV}/tools"
+
+src_unpack() {
+	tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die
+}
+
+src_prepare() {
+	epatch "${FILESDIR}/${PV}-fix_broken_icu_build.patch"
+
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i -e 's|-s\b||' \
+		build.jam || die "sed failed"
+
+	# Force regeneration
+	rm jambase.c
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(off speed space\)/\1 none/' \
+		-e 's/\(debug-symbols      : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# For slotting
+	sed -i \
+		-e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \
+		Jambase || die "sed failed"
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	newbin jam/src/bin.*/bjam bjam-${MAJOR_PV}
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build-${MAJOR_PV}
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+
+	dodoc doc/userman.pdf changes.txt hacking.txt release_procedure.txt \
+		notes/build_dir_option.txt notes/relative_source_paths.txt
+
+	if use examples ; then
+		insinto /usr/share/doc/${PF}
+		doins -r example
+	fi
+}
+
+src_test() {
+	cd jam/test
+	./test.sh || die "tests failed"
+}
diff --git a/dev-util/boost-build/boost-build-1.36.0.ebuild b/dev-util/boost-build/boost-build-1.36.0.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.36.0.ebuild
@@ -0,0 +1,104 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.36.0.ebuild,v 1.3 2009/10/24 09:20:57 vapier Exp $
+
+EAPI="2"
+
+inherit flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))"
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+LICENSE="Boost-1.0"
+SLOT="1.36"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
+IUSE="examples python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	!<=dev-util/boost-build-1.35.0-r1
+	python? ( dev-lang/python )"
+RDEPEND="${DEPEND}"
+
+S="${WORKDIR}/boost_${MY_PV}/tools"
+
+src_unpack() {
+	tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die
+}
+
+src_prepare() {
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i -e 's|-s\b||' \
+		build.jam || die "sed failed"
+
+	# Force regeneration
+	rm jambase.c
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(off speed space\)/\1 none/' \
+		-e 's/\(debug-symbols      : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# For slotting
+	sed -i \
+		-e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \
+		Jambase || die "sed failed"
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	newbin jam/src/bin.*/bjam bjam-${MAJOR_PV}
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build-${MAJOR_PV}
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+
+	dodoc doc/userman.pdf changes.txt hacking.txt release_procedure.txt \
+		notes/build_dir_option.txt notes/relative_source_paths.txt
+
+	if use examples ; then
+		insinto /usr/share/doc/${PF}
+		doins -r example
+	fi
+}
+
+src_test() {
+	cd jam/test
+	./test.sh || die "tests failed"
+}
diff --git a/dev-util/boost-build/boost-build-1.37.0.ebuild b/dev-util/boost-build/boost-build-1.37.0.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.37.0.ebuild
@@ -0,0 +1,104 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.37.0.ebuild,v 1.3 2009/10/24 09:20:57 vapier Exp $
+
+EAPI="2"
+
+inherit flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))"
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+LICENSE="Boost-1.0"
+SLOT="1.37"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
+IUSE="examples python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	!<=dev-util/boost-build-1.35.0-r1
+	python? ( dev-lang/python )"
+RDEPEND="${DEPEND}"
+
+S="${WORKDIR}/boost_${MY_PV}/tools"
+
+src_unpack() {
+	tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die
+}
+
+src_prepare() {
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i -e 's|-s\b||' \
+		build.jam || die "sed failed"
+
+	# Force regeneration
+	rm jambase.c
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(off speed space\)/\1 none/' \
+		-e 's/\(debug-symbols      : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# For slotting
+	sed -i \
+		-e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \
+		Jambase || die "sed failed"
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	newbin jam/src/bin.*/bjam bjam-${MAJOR_PV}
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build-${MAJOR_PV}
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+
+	dodoc doc/userman.pdf changes.txt hacking.txt release_procedure.txt \
+		notes/build_dir_option.txt notes/relative_source_paths.txt
+
+	if use examples ; then
+		insinto /usr/share/doc/${PF}
+		doins -r example
+	fi
+}
+
+src_test() {
+	cd jam/test
+	./test.sh || die "tests failed"
+}
diff --git a/dev-util/boost-build/boost-build-1.39.0.ebuild b/dev-util/boost-build/boost-build-1.39.0.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.39.0.ebuild
@@ -0,0 +1,104 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.39.0.ebuild,v 1.2 2009/10/24 09:20:57 vapier Exp $
+
+EAPI="2"
+
+inherit flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))"
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+LICENSE="Boost-1.0"
+SLOT="$(get_version_component_range 1-2)"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
+IUSE="examples python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	!<=dev-util/boost-build-1.35.0-r1
+	python? ( dev-lang/python )"
+RDEPEND="${DEPEND}"
+
+S="${WORKDIR}/boost_${MY_PV}/tools"
+
+src_unpack() {
+	tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die
+}
+
+src_prepare() {
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i -e 's|-s\b||' \
+		build.jam || die "sed failed"
+
+	# Force regeneration
+	rm jambase.c
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(off speed space\)/\1 none/' \
+		-e 's/\(debug-symbols      : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# For slotting
+	sed -i \
+		-e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \
+		Jambase || die "sed failed"
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	newbin jam/src/bin.*/bjam bjam-${MAJOR_PV}
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build-${MAJOR_PV}
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+
+	dodoc changes.txt hacking.txt release_procedure.txt \
+		notes/build_dir_option.txt notes/relative_source_paths.txt
+
+	if use examples ; then
+		insinto /usr/share/doc/${PF}
+		doins -r example
+	fi
+}
+
+src_test() {
+	cd jam/test
+	./test.sh || die "tests failed"
+}
diff --git a/dev-util/boost-build/boost-build-1.40.0.ebuild b/dev-util/boost-build/boost-build-1.40.0.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.40.0.ebuild
@@ -0,0 +1,104 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.40.0.ebuild,v 1.2 2009/10/24 09:20:57 vapier Exp $
+
+EAPI="2"
+
+inherit flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))"
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+LICENSE="Boost-1.0"
+SLOT="$(get_version_component_range 1-2)"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
+IUSE="examples python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	!<=dev-util/boost-build-1.35.0-r1
+	python? ( dev-lang/python )"
+RDEPEND="${DEPEND}"
+
+S="${WORKDIR}/boost_${MY_PV}/tools"
+
+src_unpack() {
+	tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die
+}
+
+src_prepare() {
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i -e 's|-s\b||' \
+		build.jam || die "sed failed"
+
+	# Force regeneration
+	rm jambase.c
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(off speed space\)/\1 none/' \
+		-e 's/\(debug-symbols      : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# For slotting
+	sed -i \
+		-e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \
+		Jambase || die "sed failed"
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	newbin jam/src/bin.*/bjam bjam-${MAJOR_PV}
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build-${MAJOR_PV}
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+
+	dodoc changes.txt hacking.txt release_procedure.txt \
+		notes/build_dir_option.txt notes/relative_source_paths.txt
+
+	if use examples ; then
+		insinto /usr/share/doc/${PF}
+		doins -r example
+	fi
+}
+
+src_test() {
+	cd jam/test
+	./test.sh || die "tests failed"
+}
diff --git a/dev-util/boost-build/boost-build-1.41.0.ebuild b/dev-util/boost-build/boost-build-1.41.0.ebuild
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/boost-build-1.41.0.ebuild
@@ -0,0 +1,111 @@
+# Copyright 1999-2009 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.41.0.ebuild,v 1.1 2009/12/02 15:25:01 djc Exp $
+
+EAPI="2"
+
+inherit flag-o-matic toolchain-funcs versionator
+
+MY_PV=$(replace_all_version_separators _)
+MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))"
+
+DESCRIPTION="A system for large project software construction, which is simple to use and powerful."
+HOMEPAGE="http://www.boost.org/doc/tools/build/index.html"
+SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2"
+LICENSE="Boost-1.0"
+SLOT="$(get_version_component_range 1-2)"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
+IUSE="examples python"
+
+DEPEND="!<dev-libs/boost-1.34.0
+	!<=dev-util/boost-build-1.35.0-r1
+	python? ( dev-lang/python )"
+RDEPEND="${DEPEND}"
+
+S="${WORKDIR}/boost_${MY_PV}/tools"
+
+pkg_setup() {
+	ewarn "Compilation of boost-build is known to break if {C,LD}FLAGS contain"
+	ewarn "extra white space (bug 293652)"
+}
+
+src_unpack() {
+	tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die
+}
+
+src_prepare() {
+	epatch "${FILESDIR}/boost-1.41-fix-mpich2-detection.patch"
+
+	# Remove stripping option
+	cd "${S}/jam/src"
+	sed -i -e 's|-s\b||' \
+		build.jam || die "sed failed"
+
+	# Force regeneration
+	rm jambase.c
+
+	# This patch allows us to fully control optimization
+	# and stripping flags when bjam is used as build-system
+	# We simply extend the optimization and debug-symbols feature
+	# with empty dummies called 'none'
+	cd "${S}/build/v2"
+	sed -i \
+		-e 's/\(off speed space\)/\1 none/' \
+		-e 's/\(debug-symbols      : on off\)/\1 none/' \
+		tools/builtin.jam || die "sed failed"
+}
+
+src_compile() {
+	cd jam/src
+	local toolset
+
+	if [[ ${CHOST} == *-darwin* ]] ; then
+		toolset=darwin
+	else
+		# Using boost's generic toolset here, which respects CC and CFLAGS
+		toolset=cc
+	fi
+
+	append-flags -fno-strict-aliasing
+
+	# For slotting
+	sed -i \
+		-e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \
+		Jambase || die "sed failed"
+
+	# The build.jam file for building bjam using a bootstrapped jam0 ignores
+	# the LDFLAGS env var (bug #209794). We have now two options:
+	# a) change the cc-target definition in build.jam to include separate compile
+	#    and link targets to make it use the LDFLAGS var, or
+	# b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var
+	#    (which should not be set by us).
+	if [[ -z "${LDFLAGS}" ]] ; then
+		CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \
+			|| die "building bjam failed"
+	else
+		LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \
+			$(use_with python) || die "building bjam failed"
+	fi
+}
+
+src_install() {
+	newbin jam/src/bin.*/bjam bjam-${MAJOR_PV}
+
+	cd "${S}/build/v2"
+	insinto /usr/share/boost-build-${MAJOR_PV}
+	doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \
+		build kernel options tools util || die
+
+	dodoc changes.txt hacking.txt release_procedure.txt \
+		notes/build_dir_option.txt notes/relative_source_paths.txt
+
+	if use examples ; then
+		insinto /usr/share/doc/${PF}
+		doins -r example
+	fi
+}
+
+src_test() {
+	cd jam/test
+	./test.sh || die "tests failed"
+}
diff --git a/dev-util/boost-build/files/1.35.0-fix_broken_icu_build.patch b/dev-util/boost-build/files/1.35.0-fix_broken_icu_build.patch
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/files/1.35.0-fix_broken_icu_build.patch
@@ -0,0 +1,33 @@
+--- trunk/tools/build/v2/build/targets.jam (revision 45072)
++++ trunk/tools/build/v2/build/targets.jam (revision 45245)
+@@ -1170,5 +1170,5 @@
+             ECHO [ targets.indent ] "Building target '$(fn)'" ;
+             targets.increase-indent ;
+-            ECHO [ targets.indent ] "Build request: " [ $(property-set).raw ] ;
++            ECHO [ targets.indent ] "Build request: " $(property-set) [ $(property-set).raw ] ;
+             local cf = [ build-system.command-line-free-features ] ;
+             ECHO [ targets.indent ] "Command line free features: " [ $(cf).raw ] ;
+@@ -1275,5 +1275,14 @@
+                 # case we don't want any diagnostic. In the former case, we need
+                 # diagnostics. FIXME
+-                self.generated.$(property-set) = $(rproperties) ;
++                
++                # If this target fails to build, add <build>no to properties
++                # to cause any parent target to fail to build.  Except that it
++                # - does not work now, since we check for <build>no only in
++                #   common properties, but not in properties that came from
++                #   dependencies
++                # - it's not clear if that's a good idea anyway.  The alias
++                #   target, for example, should not fail to build if a dependency
++                #   fails.
++                self.generated.$(property-set) = [ property-set.create <build>no ] ;
+             }
+         }
+@@ -1283,4 +1292,7 @@
+             {
+                 ECHO [ targets.indent ] "Already built" ;
++                local ur = $(self.generated.$(property-set)) ;
++                ur = $(ur[0]) ;
++                ECHO [ targets.indent ] "  Usage requirements " [ $(ur).raw ] ;
+             }
+         }
diff --git a/dev-util/boost-build/files/boost-1.41-fix-mpich2-detection.patch b/dev-util/boost-build/files/boost-1.41-fix-mpich2-detection.patch
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/files/boost-1.41-fix-mpich2-detection.patch
@@ -0,0 +1,35 @@
+Index: tools/build/v2/tools/mpi.jam
+===================================================================
+--- tools/build/v2/tools/mpi.jam        (revision 57744)
++++ tools/build/v2/tools/mpi.jam        (working copy)
+@@ -156,14 +156,27 @@
+         # into a feature.
+         local match = [ MATCH "^(-.)(.*)" : $(cmdline) ] ;
+         local matched ;
+-        if $(match) && $(match[2]) {
++        if $(match) && $(match[2]) {
+            local prefix = $(match[1]) ;
+            if $(feature_kinds$(prefix)) {
+                local name = $(feature_kinds$(prefix)) ;
+                local add = [ add_feature $(prefix) $(name) $(cmdline) ] ;
+
+                if $(add) {
+-                  result += $(add[1]) ;
++
++                  if $(add[1]) = <find-shared-library>pthread
++                  {
++                      # Uhm. It's not really nice that this MPI implementation
++                      # uses -lpthread as opposed to -pthread. We do want to
++                      # set <threading>multi, instead of -lpthread.
++                      result += "<threading>multi" ;
++                      MPI_EXTRA_REQUIREMENTS += "<threading>multi" ;
++                  }
++                  else
++                  {
++                      result += $(add[1]) ;
++                  }
++
+                   cmdline = $(add[2]) ;
+                   matched = yes ;
+                }
+
diff --git a/dev-util/boost-build/metadata.xml b/dev-util/boost-build/metadata.xml
new file mode 100644
--- /dev/null
+++ b/dev-util/boost-build/metadata.xml
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <herd>cpp</herd>
+  <maintainer>
+    <email>dev-zero@gentoo.org</email>
+    <name>Tiziano Müller</name>
+  </maintainer>
+  <maintainer>
+    <email>djc@gentoo.org</email>
+    <name>Dirkjan Ochtman</name>
+  </maintainer>
+  <maintainer>
+    <email>s.mingramm@gmx.de</email>
+    <name>Sebastian Mingramm</name>
+  </maintainer>
+</pkgmetadata>