stephen white wrote: [snip]
>> I'm trying to make sure any tools we use to create our snapshot will be >> available to our users so they can do this own their own if they would >> like! > > > This sounds good, though it's almost there as it is... the way that > portage calculates what version to emerge in just needs to be frozen > despite later updates. So capturing the information of "which packages > are stable now, keep using those as the stable version (except for > security updates)" would accomplish this. > > To be more specific... portage calculates what packages are stable from > the x86, ~x86, ppc, ~ppc (etc etc) keywords in the ebuilds, so doing an > "emerge sync" will change that. Therein lies the problem, since which > versions to use should be snapshotted and later stable packages > shouldn't be automatically chosen. > > If all the packages were examined for what keywords they have at that > point, then that information was frozen, then I would be able to "emerge > sync" and still perform further emerges with the same software versions > as if I hadn't emerge synced... while preserving the ability to update > portage, comprehend new ebuild formats and chose where to override. > > Currently, "stable" = "latest version", which can be changed to "stable > = version in snapshot", where "snapshot = stable latest versions at that > point in time, or if no snapshot entry, fall back to actual latest > stable version". > > I really don't think I'm explaining this well, so let me know if you > want me to try explaining again! :) The problem with this is eclasses. They aren't in a 'versioned' fashion so if you update the tree you may keep the same ebuilds as before, but the eclasses that those ebuilds use have changed. We didn't think of this at first so we were shooting at trying a locked profile for this GLEP. But we soon found out that wouldn't entirely work because of the eclass and other related problems. Eclasses are great for portage, but a PITA if you want to stablize the tree to the point of predictability. -- Lance Albertson <[EMAIL PROTECTED]> Gentoo Infrastructure --- Public GPG key: <http://www.ramereth.net/lance.asc> Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net
signature.asc
Description: OpenPGP digital signature
