On Tue, Feb 03, 2004 at 02:38:07PM +0200, Dan Armak wrote: > On Tuesday 03 February 2004 12:39, Paul de Vrieze wrote: > > The main issue that the stable keyword is trying to solve is the > > following: > > > > How can we have package maintainers indicate in an easy way those > > packages that are candidates for inclusion in the frozen tree. Those > > ebuilds can then be collected into the stable branch automatically. > > > > One solution is to ask developers to set the stable flag on an ebuild. > > The newest package with this keyword would than be included into the > > tree. > > > > There are however problems with the keywords solution. The big problem is > > that it is not easy to know which auxiliary files (patches) are needed > > for a particular ebuild. I think a better approach would be a staging > > area of some kind where the relevant ebuilds could be entered into > > (possibly in cat/package-version directories). The inclusion script > > could then test building the package and then include it into the > > to-be-frozen tree. > > > > After the frozen tree is released the staging area could be cleaned up > > (or archived for later reference). > > I understand why a keyword might be useful in marking ebuilds that'll go into > a stable branch. However, you haven't ansewred my question - why have a > separate cvs branch at all? Why not just use keywords as we do now for > arch/~arch?
My own opinion: 1. The size of the tree. If this is to be an enterprise tree, its likely that it won't have an ebuild for every package as most enterprise people won't want x (name an obscure desktop related package). Quicker synchrosing and easier backup/restore and less clutter is good. This isn't a big issue really though. 2. Guaranteed someone will "clean" an ebuild thinking its to old and needs to be removed. This is a big issue. If its a seperate tree where only people who know the rules of the tree work, its more likely to stay consistant and not have stuff removed that shouldn't be. -- rob holland - [ [EMAIL PROTECTED] ] irc://irc.freenode.net/#gentoo as tigger^ http://dev.gentoo.org/~tigger/[EMAIL PROTECTED]
pgp00000.pgp
Description: PGP signature
