Eclasses are great for portage, but a PITA if you want to stablize the tree to
the point of predictability.
<spoob> OK, my perspective is that yes, this is a issue however I believe it would affect edge cases and would not be such a problem in practice.
<spoob> Consider that a GLSA update is inherently unpredictable anyway, so that has already polluted the consistency. So it's just about trying to reduce the damage than achieving an ideal result
<spoob> So don't worry about the versioned eclasses, but go ahead with the snapshotting.
...
<spoob> i don't see it as a solvable problem since it's already changed so predictability is not achievable
<spoob> but a 90% of the result for 10% of the effort solution may be easy and worthwhile
<spoob> for the time being I'm going to try nailing all the versions and see what problems I find over time
<spoob> (other than portage gagging on a 90,000 line make.profile/packages :)
...
<spoob> oh, I have an interesting idea. i think
<spoob> it's very brutal but I think it is simple and effective
<spoob> emerge sync, update everything as normal, no changes to portage
<spoob> but when emerge'ing something, specify all the versions (via a snapshot tool?) for all the dependencies all the way down
<spoob> and if there's any problem, then emerge can issue its normal complaint that this version is no longer available, or that version which is security bumped requires a later version of something or other
<spoob> since it's not a completely solvable problem, just do the best it can and tell me what it can't do and I can make up my mind what to do at that point, instead of doing a Windows and trying to do it anyway but failing to do it right.
<spoob> to implement that will just be a snapshot of what is stable right now, then feeding all that information to portage (which has its latest tree so it is operating up to date) as a user preference.
<spoob> the same way I could do emerge =apache1.3 and get told it isn't available
<spoob> OK, nobody here, so will cut/paste this as my response to the email. :)
So I guess this is amended to portage just doing its best and telling me when it can't do it. That way I'm the sysadmin making the decision what to do with a changed machine - eg, I could decided to update the whole system and re-QA it.
Interesting chat, thanks.
-- [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.
