On Tue, 01 Apr 2003 09:01:52 -0800, Susie wrote:
> 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).
Here is what i did:
# ACCEPT_KEYWORDS=~x86 emerge openbox
which installed 2.3.0
> 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).
Maybe the trouble here comes from --deep? Because 'emerge -pU world'
doesn't say anything about openbox, given you pinned the version to
2.3.0 in the world file.
> 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>
That's a bug in the ebuild. Since 2.1.3-r4 and 2.3.0 uses different
slots they shouldn't overwrite each other. You could file it on
Bugzilla.
Also: What Daniel suggested (-U) doesn't work because of the different
slots as well.
--
[EMAIL PROTECTED] mailing list
