| 1 |
On Tuesday 03 February 2004 12:39, Paul de Vrieze wrote: |
| 2 |
> The main issue that the stable keyword is trying to solve is the |
| 3 |
> following: |
| 4 |
> |
| 5 |
> How can we have package maintainers indicate in an easy way those |
| 6 |
> packages that are candidates for inclusion in the frozen tree. Those |
| 7 |
> ebuilds can then be collected into the stable branch automatically. |
| 8 |
> |
| 9 |
> One solution is to ask developers to set the stable flag on an ebuild. |
| 10 |
> The newest package with this keyword would than be included into the |
| 11 |
> tree. |
| 12 |
> |
| 13 |
> There are however problems with the keywords solution. The big problem is |
| 14 |
> that it is not easy to know which auxiliary files (patches) are needed |
| 15 |
> for a particular ebuild. I think a better approach would be a staging |
| 16 |
> area of some kind where the relevant ebuilds could be entered into |
| 17 |
> (possibly in cat/package-version directories). The inclusion script |
| 18 |
> could then test building the package and then include it into the |
| 19 |
> to-be-frozen tree. |
| 20 |
> |
| 21 |
> After the frozen tree is released the staging area could be cleaned up |
| 22 |
> (or archived for later reference). |
| 23 |
|
| 24 |
I understand why a keyword might be useful in marking ebuilds that'll go into |
| 25 |
a stable branch. However, you haven't ansewred my question - why have a |
| 26 |
separate cvs branch at all? Why not just use keywords as we do now for |
| 27 |
arch/~arch? |
| 28 |
|
| 29 |
-- |
| 30 |
Dan Armak |
| 31 |
Gentoo Linux developer (KDE) |
| 32 |
Matan, Israel |
| 33 |
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key |
| 34 |
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951 |
Archives