With your own profile you can accomplish what you're outlining above. If
you're lazy like me you could wait for GLEP 19.
glsa-check should over-ride my make.profile/packages configuration though? That's a minor detail though... the important thing is for me to be able to lock down my own stable packages, because I don't believe that using an external stable tree will provide help against deployment specific issues - hence QA is always the user's problem.
What's a good lazy way of locking all the stable packages in my profile? I'm a bit worried about dumping 90,000 lines into make.profile/packages since I expect portage will slow down and choke (will have to try and see!). Let me know if there's any interest and I'll report back with the results and likely a document detailing how to use portage with this approach.
-- [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.
