I am probably wrong, but I thought that portage would only install a new slot if either it was required by a package or the package is in your world file?
On Wed, 2005-06-01 at 00:18 +0900, Jason Stubbs wrote: > On Wednesday 01 June 2005 00:06, Holly Bostick wrote: > > The short version is that, after my previous thread about removing an > > extra version of Python (2.4.1 when I already had 2.3.5 installed), > > Portage now wants to re-emerge Python 2.4.1, and I can't seem to prevent > > it. > > <snip> > > > I just don't see where Python 2.4.1 is coming from (since everything in > > the -D tree for it was perfectly fine with Python 2.3.5), and the new > > stuff that originally installed it is a) being downgraded to a version > > that should be (or was previously) fine with 2.3.5, and b) does not seem > > to specifically require 2.4.1; if Python is mentioned in the > > dependencies of one of them-- and the only one that does mention it is > > dbus, and that only with the USE flag set-- the requirement is a >= , > > not an =2.4.1. > > Portage is seeing that an upgrade is available (regardless of the slot) and > offering to upgrade it. Little notice is taken of slots at present, but I > would call the above behaviour correct even if they were. > > > 1) am I panicking over nothing > > Yup! ;) > > > 2) if I am not panicking over nothing, how do I stop this juggernaut > > before it lands me in the soup again? > > Remove whatever you did to unmask it. /etc/portage/package.unmask perhaps? > > Regards, > Jason Stubbs -- [email protected] mailing list
