Andy Dustman schrieb: > SYNC="rsync://rsync.gentoo.org/gentoo-releases" > RELEASE="2006.1" > RELEASE_OVERLAYS="updates security" > > Doing a emerge --sync would then perform the following: > > * rsync://rsync.gentoo.org/gentoo-releases/2006.1 to $PORTDIR > * rsync://rsync.gentoo.org/gentoo-releases/2006.1-updates to > $PORTDIR-updates > * rsync://rsync.gentoo.org/gentoo-releases/2006.1-security to > $PORTDIR-security > > $PORTDIR-updates and $PORTDIR-security could then be treated as > implicit PORTDIR_OVERLAYs. SYNC could be overridden in /etc/make.conf > as it is now. If you wanted only security updates, then you could set > RELEASE_OVERLAYS="security" in make.conf. Disclaimer: I'm not trying to shoot you down, just ask some questions...
> > This is now three trees to sync against >From which two don't exist (yet). You need to specify how they should be generated and maintained. > instead of one, but the > important feature is that the primary tree is now static data, could be the snapshot coming with the release... > once it > is done as a final release, so there is only the timestamp check; and > the other two trees should be relatively small. Obsolete ebuilds need > only be removed when there is a new release, and this happens in a > different tree. Potentially, only packages with at least one stable > arch flag could go in updates; anything that is all ~arch or masked > could go into a separate testing overlay. If you dont set ~ARCH why are you concerned about ~arch ebuilds? If this is about space saving or cutting down sync time/resources you need to explain how the "security" and "updates" branches would be maintained and integrated. cheers Paul -- [email protected] mailing list
