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? -- Dan Armak Gentoo Linux developer (KDE) Matan, Israel Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951
pgp00000.pgp
Description: signature
