-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 03 February 2004 11:04, Dan Armak wrote: > On Monday 02 February 2004 17:17, Kurt Lieber wrote: > > Please take a moment to review the GLEP and offer any feedback or > > ask any questions. > > If we're introducing stable keywords, why do we need a cvs branch? So > far keywords have been used to identify logical trees and people have > been talking about changing the cvs/rsync setup somehow to allow users > to fetch a tree with just the keywords they want. Ebuild revision > numbers allow different ebuilds for different keywords/trees for the > same package version. > > A real separate cvs branch seems like a lot of extra work; most > updates going into the stable branch will probably also go into the > main tree. What am I missing?
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). Paul - -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAH3pLbKx5DBjWFdsRAtBfAJ0T2U2E9BJOuTLeg+pYKQ9lp+yJ4gCgzg1r 3chMmj9mtV2nGvUJOKMH804= =uUId -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
