On Mon, Dec 10, 2007 at 07:18:26AM +0000, Ciaran McCreesh wrote:
> On Sun, 9 Dec 2007 20:31:46 -0800
> Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> > On 18:57 Sun 09 Dec     , Ciaran McCreesh wrote:
> > > On Sun, 09 Dec 2007 19:45:27 +0100
> > > Jan Kundr??t <[EMAIL PROTECTED]> wrote:
> > > > What is the point of using version information along the scm
> > > > suffix?
> > > 
> > > Branches.
> > 
> > How would I handle branches that aren't numbers but are instead
> > strings, which seems to grow increasingly more common as VCSs can
> > handle it? Just give them arbitrary numbers?
> Feature as opposed to release branches would still have to be separate
> packages, especially if you need to depend upon a particular feature.
What I've got for my Xorg testing setup, is foo-9999-rX, with a number
of different -X values that I just select from via package.{un,}mask
while testing - this saves altering everything else in the tree to pick
some package that has a different name just to satisfy a branch (which
also requires lots of ${MY_PN} mockery for some packages.
You'd also need to put '!cat/pn-feat' in the base cat/pn package and

Are SCM packages that heavily used that we need to support multiple
branches with dependencies between them?

There's two cases of branches I see (irrelevant of the names used):
Major version branches - eg CVS "cvs-1.11.x" and "cvs-1.12.x" 
(those are the actual upstream branch names, I've seen other packages
using the branch names of 'STABLE', 'OLDSTABLE', 'FEATURE').
Feature-development branches - short-lived branches for the
development of a specific feature - eg the 'atombios-support' branch of
the xorg-video-ati driver (Heavily used in Git repos, where they are
deleted on completion).

Any more styles of branches that other folk have seen?

Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

Attachment: pgpRWwimfpujm.pgp
Description: PGP signature

Reply via email to