-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sybren Stuvel wrote:
> Thomas Hafner enlightened us with:
>
>>I can put a line into /etc/portage/package.keywords to emerge it:
>>
>>=foo/bar-0.42
>>
>>Then I test the package and I'm lucky with it. I'm *not* interested
>>in future versions >0.42, if they are also masked, because I don't
>>want to repeat the tests. But I'm very interested in future versions
>>
>>>0.42, which are *not* masked at all.
>>
>>Can I achieve that in an easy, automatical way?
>
>
> Yes. Stop worrying and let Portage do it's thing. It's already set up
> like that ;-)
>
> Sybren

Hi,
There is one problem here. After a while, the masked 0.42 ebuild might
be replaced with, say 0.43, also masked. The next emerge sync will
delete the 0.42 and replace it with 0.43. Since you haven't unmasked
0.43, it can't upgrade. When you run emerge -uatvDN world, it will then
try to DOWNGRADE the package. 0.42 "doesn't exist" any more, so it'll
ask you to downgrade to, say, 0.38 (latest not-masked package). I
discovered this with PHP.

I'm not sure what the proper solution for this is. My solution involved
copying the PHP 5.0.3 ebuild and its associated files from the Portage
tree and putting them into my overlay. This keeps them available to
Portage, which then doesn't keep bugging me to downgrade. Once something
above 5.0.3 is available AND STABLE, Portage will happily upgrade, and I
can delete my overlay.

Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)

iD8DBQFCwzkcgxSrXuMbw1YRAtK/AJ9ibEzdQB39khYoS+uQigUIReFiIQCgmpBC
G0EZf1fUpsFInnKdSMq4DPc=
=TD6M
-----END PGP SIGNATURE-----