| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Tuesday 03 February 2004 11:04, Dan Armak wrote: |
| 5 |
> On Monday 02 February 2004 17:17, Kurt Lieber wrote: |
| 6 |
> > Please take a moment to review the GLEP and offer any feedback or |
| 7 |
> > ask any questions. |
| 8 |
> |
| 9 |
> If we're introducing stable keywords, why do we need a cvs branch? So |
| 10 |
> far keywords have been used to identify logical trees and people have |
| 11 |
> been talking about changing the cvs/rsync setup somehow to allow users |
| 12 |
> to fetch a tree with just the keywords they want. Ebuild revision |
| 13 |
> numbers allow different ebuilds for different keywords/trees for the |
| 14 |
> same package version. |
| 15 |
> |
| 16 |
> A real separate cvs branch seems like a lot of extra work; most |
| 17 |
> updates going into the stable branch will probably also go into the |
| 18 |
> main tree. What am I missing? |
| 19 |
|
| 20 |
The main issue that the stable keyword is trying to solve is the |
| 21 |
following: |
| 22 |
|
| 23 |
How can we have package maintainers indicate in an easy way those |
| 24 |
packages that are candidates for inclusion in the frozen tree. Those |
| 25 |
ebuilds can then be collected into the stable branch automatically. |
| 26 |
|
| 27 |
One solution is to ask developers to set the stable flag on an ebuild. |
| 28 |
The newest package with this keyword would than be included into the |
| 29 |
tree. |
| 30 |
|
| 31 |
There are however problems with the keywords solution. The big problem is |
| 32 |
that it is not easy to know which auxiliary files (patches) are needed |
| 33 |
for a particular ebuild. I think a better approach would be a staging |
| 34 |
area of some kind where the relevant ebuilds could be entered into |
| 35 |
(possibly in cat/package-version directories). The inclusion script |
| 36 |
could then test building the package and then include it into the |
| 37 |
to-be-frozen tree. |
| 38 |
|
| 39 |
After the frozen tree is released the staging area could be cleaned up |
| 40 |
(or archived for later reference). |
| 41 |
|
| 42 |
Paul |
| 43 |
|
| 44 |
- -- |
| 45 |
Paul de Vrieze |
| 46 |
Gentoo Developer |
| 47 |
Mail: pauldv@g.o |
| 48 |
Homepage: http://www.devrieze.net |
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 51 |
|
| 52 |
iD8DBQFAH3pLbKx5DBjWFdsRAtBfAJ0T2U2E9BJOuTLeg+pYKQ9lp+yJ4gCgzg1r |
| 53 |
3chMmj9mtV2nGvUJOKMH804= |
| 54 |
=uUId |
| 55 |
-----END PGP SIGNATURE----- |
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-dev@g.o mailing list |
Archives