I think that you can do: emerge -pUD world
which will keep portage from downgrading anything -daniel On Tue, 2003-04-01 at 10:01, Susie wrote: > On Tue, 01 Apr 2003 15:50:56 +0200 > Alexander Futasz <[EMAIL PROTECTED]> wrote: > > > > What are you talking about? > > I unmasked openbox-2.3.0 in it's ebuild. Then emerged it. I then put > into my world file "=x11-wm/openbox-2.3.0" to prevent it from removing > that version(ie downgrading). But despite that it fetched > openbox-2.1.3-r4. Now if you look in the changelog for openbox the > 2.3.0 is simply masked for those that don't use xft2. I have xft2 > installed so not a problem. When I installed version 2.3.0 I had > uninstalled 2.1.3-r4. But then later did an "emerge rsync && emerge > -puD world"(aka --pretend --update --deep). Then it insisted on the > earlier version overwriting the openbox in /usr/bin(as it isn't > attaching version numbers to the executable). I want it to stop doing > that.<sigh> I suppose my only option at this point is to leave both in > and unmask the 2.3.0 again and have it overwrite the earlier version. -- [EMAIL PROTECTED] mailing list
