But the way I would do it is to simply not sync the main Portage tree. Instead maintain a small security/bug fix/custom overlay.
With the sheer volume of security updates, this is a rather labour intensive method. I just want to be able to update without redefining what "stable" means - eg, gimme the info, but don't change my system while you're at it!
The basic problem is that the "stable vs unstable" definition is in the ebuild, whereas it seems it should be factored out into a list or some other representation so there's not so many problems trying to pull the desired information out or operate on that information.
Sadly, ebuilds appear to be diverging significantly from the original idea of just capturing the commands that would be typed in to install programs, and more towards its own language while continuing to retain the disadvantages of shell grammar...
Anyway, thanks for the information and I shall try a few things then report back.
-- [EMAIL PROTECTED]
CRICOS Provider Number 00123M ------------------------------------------------ This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient.
