1 Jan
2020
1 Jan
'20
1:21 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Personally I think it is still better to have a master and r14.0.x branch. For all
maintenance releases (like R14.0.x)
the various ebuild scripts can leave within the same branch, but at least when we change
into a new minor release
there is a clear separation between branches. Just my 2 cents.
Cheers
Michele
Splitting all
of this into "master" and "stable" branches only means that the people
pulling the "stable" branch
might get stale/broken/no 9999 ebuilds. It just isn't supposed to work like that.
If you'd like a sample of how this kind of thing looks in practice, here's
poppler in the official Gentoo ebuild
repository, with three release ebuilds and one live ebuild:
https://gitweb.gentoo.org/repo/gentoo.git/tree/app-text/poppler
Thank you, now I understand better. This means there is no need to create a branch. It
also means that
tde-packaging-gentoo will not be part of the 'tde' tree on r14.0.x branch.
Is there also a convention for preliminary packages? For example, as on Debian
"~preXX", or on FreeBSD "+pXX"?
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl4MZIgACgkQKnW3yore
1c8U4w/+IHwYlpZEuOrXUwS5UMAgXkFY8bgXwPHoP0g3yIyL+u1rVVnq4+0wDVyp
HCHPOM5O2zyE68xFd6THorlgOHM8xEqo3GbFZ27npZSq4L8qRMUKipm+VNIFawNp
AV57ZAMlQtkyw3tF/Dy+bWAfczeCTjRwGtTSQgKecSRUkT6yxXpwnzYrdPjc1RxR
nfAkk0gqAHqJx394cBqo6V9AVFiC9kecGrYGgRnTeBp92p3axXyaprACmv8Vuu7n
W7KIPayXtbQgANbDO/e9198wN7JAsaQKkKVkcN5eXoNo8i4SHmmj6O3PtM86zDAq
X3+49fDJ/erZBJqo3Rk53vUsx52YBz/nquZvErZg1Lx9feMnAryLncRdDbF0om+L
svMCzdU5rS21encSeejdkHxAhMoSuycNb7cj8iidg/UCGHOmZvn2vt3mGZ9Uy9GN
DsJYHAr5D9BBeKq3bmIUebR4IRBfcslFt+Z2A9x4R4fitnXEJEKzXpDCAPQgSRjF
Mfp+5+lgGFmQllKM+0nN2uUgw71HGMHDEzehWL1mJl3cRE+WNvkXWqkvCkCtAebK
ylqWVgnw2AqEUUFCiQimPmy3resi3yWcfAx/zvaiiG40g6nMUDXLGxPjfFVkbrA7
vVVxMpTr5hF7pk7kIIZYIG3ATxNXcigH2gjCrQgFojLTcf71fKA=
=2m98
-----END PGP SIGNATURE-----