On Mon, Aug 09, 2004 at 10:21:09AM -0400 or thereabouts, Chris Gianelloni wrote:
> Fork into a completely new module.

I don't think this is a very good idea for reasons that I'll discuss below.

> Take any and all ebuilds which are marked as stable for a particular
> arch, remove any ~arch keywords, and split it to a gentoo-$version
> module.  

Agreed, though I don't see a real need to remove ~arch ebuilds.

> Since it is a separate module, the ebuilds will always be
> there.  Since it was taken from the release snapshot for each arch,
> it'll also match what is done on the release media, making bug hunting
> even easier.  

[side note] the releases of the tree are not tied to the releases of our
liveCD/package sets.[/side note]

> Here, we're using the SYNC variable to control the tree, rather than a
> profile.  This means we can support multiple profiles on the same tree
> easily, and also keeps ebuilds around for as long as we keep the tree
> around.

One think that I think *everyone* agrees on is that any stable tree needs
to be regularly updated with security fixes.  With this in mind, I'm
concerned with trying to maintain multiple separate SYNC modules.  We'd
have to upgrade each one with every GLSA, thus doubling or tripling the
amount of CVS work needed each time.

--kurt