On Tue, Feb 03, 2004 at 10:37:50AM -0500 or thereabouts, Chris Gianelloni wrote: > I still like the idea of separate rsync branches. > > gentoo-2004.0-stable and gentoo-2004.0-updates, both taken via rsync > with -stable being static per release and -updates being dynamic and an > overlay to ensure it always overrides the -stable unless a user emerges > a =cat/ver combo from stable.
So if I understand you correctly, you're suggesting having a total of 8 rsync branches: gentoo-2004.0-stable gentoo-2004.0-updates gentoo-2004.1-stable gentoo-2004.1-updates ... gentoo-2004.3-updates Is that correct? If so, I like the idea in theory, but how do you make sure security fixes get into all the appropriate trees? I can see a huge QA nightmare with devs forgetting to include some critical security fix in the older trees. Then there's the whole issue of dependencies of security updates that I mentioned in my reply to danarmak. That would still be a problem here. We could write a whole crapload of logic into repoman so it could help with this, but that's a lot more invasive than I had planned on this GLEP being. That said, I do like the idea if you can help me understand how it's manageable without being overly cumbersome to implement. > Dual portage trees requires no portage changes as portage supports > multiple overlays now. OK, good to know. I wasn't sure if this was fully functional yet. That said, is it easy to use? Can I type "emerge sync --updates-overlay" or something similar? If we're expecting users to use rsync directly, then I think that's probably unrealistic. --kurt
pgp00000.pgp
Description: PGP signature
