Add a safeguard to prevent someone from accidently using this profile without knowing...

diff --git a/profiles/default-linux/amd64/multilib-dev/README b/profiles/default-linux/amd64/multilib-dev/README
index a6796a06da61fcf44aaa7a418479da09df10efe3..67cea5c22ca52e96c234d0f62e905b9a822bfdcd 100644 (file)
--- a/profiles/default-linux/amd64/multilib-dev/README
+++ b/profiles/default-linux/amd64/multilib-dev/README
@@ -41,3 +41,7 @@ report as not everything is in the latest portage release.
 
 [1] http://bugs.gentoo.org/show_bug.cgi?id=75420
 
+I have added a check to make sure someone doesn't use this profile without
+knowing these risks.  Please set a variable 'IWANTTOTRASHMYSYSTEM' in your
+/etc/make.conf if you really want to test this profile.
+

diff --git a/profiles/default-linux/amd64/multilib-dev/packages b/profiles/default-linux/amd64/multilib-dev/packages
index 7fe394b42d44d8946a0f352b50701c1552f794d5..5c73d128f8ee68a35f43dc0379971765ba7f589e 100644 (file)
--- a/profiles/default-linux/amd64/multilib-dev/packages
+++ b/profiles/default-linux/amd64/multilib-dev/packages
@@ -1,12 +1,9 @@
 # Copyright 1999-2004 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/amd64/multilib-dev/packages,v 1.1 2005/01/01 00:44:50 eradicator Exp $
-
-# Our gcc goes in /usr/lib/gcc rather than /usr/lib/gcc-bin
-*>=sys-devel/gcc-config-1.3.7-r5
+# $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/amd64/multilib-dev/packages,v 1.2 2005/01/04 12:26:39 eradicator Exp $
 
 # Force toolchain versions that have been tested to work and are multilib aware
-*>=sys-apps/portage-2.0.51-r8
+*>=sys-apps/portage-2.0.51-r9
 *>=sys-devel/binutils-2.15.92.0.2-r2
 *>=sys-devel/gcc-3.4.3-r1
 *>=sys-libs/glibc-2.3.4.20040808-r1

diff --git a/profiles/default-linux/amd64/multilib-dev/profile.bashrc b/profiles/default-linux/amd64/multilib-dev/profile.bashrc
new file mode 100644 (file)
index 0000000..9cd1243
--- /dev/null
+++ b/profiles/default-linux/amd64/multilib-dev/profile.bashrc
@@ -0,0 +1,33 @@
+# fix for bug 60147, "configure causes sandbox violations when lib64
+# is a directory". currently only works with cvs portage.
+#SANDBOX_WRITE="${SANDBOX_WRITE}:/usr/lib64/conftest:/usr/lib64/cf"
+addwrite /usr/lib64/conftest
+addwrite /usr/lib64/cf
+
+# oh goodie, yet ANOTHER sandbox bug!!!! >:|
+# without portage 2.0.51 and the following entries, at least dbus will spew
+# sandbox violations like mad with python in lib64.
+addpredict /usr/lib64/python2.0/
+addpredict /usr/lib64/python2.1/
+addpredict /usr/lib64/python2.2/
+addpredict /usr/lib64/python2.3/
+addpredict /usr/lib64/python2.4/
+addpredict /usr/lib64/python2.5/
+addpredict /usr/lib64/python3.0/
+
+# sandbox is disabled for /dev/null by default, so this bug isnt caught.
+# hopefully this will help us figure out where this problem occurs...
+if [ ! -e /dev/null ] ; then
+       eerror "/dev/null doesnt exist! this is bad! tail -n 20 /var/log/emerge.log and attach the output to http://bugs.gentoo.org/show_bug.cgi?id=65876"
+       exit 1
+elif [ -f /dev/null ] ; then
+       eerror "/dev/null is a normal file! this is bad! tail -n 20 /var/log/emerge.log and attach the output to http://bugs.gentoo.org/show_bug.cgi?id=65876"
+       exit 1
+fi
+
+if [ -n "${IWANTTOTRASHMYSYSTEM}" ]; then
+       echo "You are using a VERY development profile.  You probably"
+       echo "shouldn't be doing this.  Please see the README in"
+       echo "/usr/portage/profiles/default-linux/amd64/multilib-dev"
+fi
+

diff --git a/profiles/default-linux/sparc/sparc64-multilib/dev/README b/profiles/default-linux/sparc/sparc64-multilib/dev/README
index dd3127d0b143343a831241b4c3d1f23361e366eb..ea2cda8e1a21c0b9963862301dda5a3b80ade4c4 100644 (file)
--- a/profiles/default-linux/sparc/sparc64-multilib/dev/README
+++ b/profiles/default-linux/sparc/sparc64-multilib/dev/README
@@ -18,3 +18,7 @@ If you use this profile or you have any questions, please contact me on IRC.
 
 --Jeremy
 eradicator@gentoo.org
+
+I have added a check to make sure someone doesn't use this profile without
+knowing these risks.  Please set a variable 'IWANTTOTRASHMYSYSTEM' in your
+/etc/make.conf if you really want to test this profile.

diff --git a/profiles/default-linux/sparc/sparc64-multilib/profile.bashrc b/profiles/default-linux/sparc/sparc64-multilib/profile.bashrc
index 951d75d73b92005897a996cf9927cde4d7506dae..47fa4142271bc3aedbd39c8d1bce1c8f7ca2aa64 100644 (file)
--- a/profiles/default-linux/sparc/sparc64-multilib/profile.bashrc
+++ b/profiles/default-linux/sparc/sparc64-multilib/profile.bashrc
@@ -15,3 +15,9 @@ addpredict /usr/lib64/python2.3/
 addpredict /usr/lib64/python2.4/
 addpredict /usr/lib64/python2.5/
 addpredict /usr/lib64/python3.0/
+
+if [ -n "${IWANTTOTRASHMYSYSTEM}" ]; then
+       echo "You are using a VERY development profile.  You probably"
+       echo "shouldn't be doing this.  Please see the README in"
+       echo "/usr/portage/profiles/default-linux/sparc/sparc64-multilib/dev"
+fi