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

Chris Head wrote:
> Sybren Stuvel wrote:
>
>>>Chris Head enlightened us with:
>>>
>>>
>>>>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.
>>>
>>>
>>>If they really delete a version, it's for a good reason. You shouldn't
>>>use that version any more.
>>>
>>>
>>>
>>>>I'm not sure what the proper solution for this is.
>>>
>>>
>>>Upgrade to another masked version, or stick to the stable one.
>>>
>>>
>>>
>>>>My solution involved copying the PHP 5.0.3 ebuild and its associated
>>>>files from the Portage tree and putting them into my overlay.
>>>
>>>
>>>That'll do what you want. I don't reccomend it, though.
>>>
>>>
>>>
>>>>This keeps them available to Portage, which then doesn't keep
>>>>bugging me to downgrade.
>>>
>>>
>>>Again: there are always reasons for a move like that. I strongly
>>>suggest you re-think your strategy.
>>>
>>>Sybren
>
>
> Hmm. Thanks Paul and Sybren; yes, I mean that the package ACTUALLY
> DISAPPEARED from Portage! (I decided to do what I did [save it in my
> overlay] because I was under the impression that this was a normal
> thing; otherwise after ten releases of a package your Portage tree would
> start to get very big). Unfortunately using a stable version is not an
> option at this time (I'd like to go stable, but I can't stand PHP4...
> anyone know when PHP5 is going stable?) Unfortunately this meant I had
> to upgrade Apache, APR, APR-util, and Gentoo-webroot-default all to
> unstable versions (I've just bitten the bullet and done it). I guess
> once PHP5 becomes stable I'll slowly and gently start downgrading
> packages until I become stable again.
>
> Chris

Hi again,
The moment after I posted this message I actually tried to update world,
and discovered that this won't work. Apache 2.0.54-r10 blocks
Subversion, and I really don't want to go crazy with my source control
system. I guess it's back to PHP 5.0.3 until something becomes stable
again... I know it's not the recommended way, but I simply can't seem to
figure out how to do it right without making a giant cascade of unstable
packages. I'd rather have ONE bad package than ten unstable (since it's
only a development server anyway).

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

iD8DBQFCxBTzgxSrXuMbw1YRAjeXAJ4pIharHkj8/PiCUIHpV6KCZMxtAQCcCsYG
v9Ai2hs28AwEDZCfZPJm4B8=
=eGZi
-----END PGP SIGNATURE-----