From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [GLEP] scm package version suffix
Date: Mon, 10 Dec 2007 00:26:21 -0800 [thread overview]
Message-ID: <20071210082621.GF14557@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <20071210071826.465f7bff@blueyonder.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
On Mon, Dec 10, 2007 at 07:18:26AM +0000, Ciaran McCreesh wrote:
> On Sun, 9 Dec 2007 20:31:46 -0800
> Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > On 18:57 Sun 09 Dec , Ciaran McCreesh wrote:
> > > On Sun, 09 Dec 2007 19:45:27 +0100
> > > Jan Kundr??t <jkt@gentoo.org> 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
vice-versa.
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
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 321 bytes --]
next prev parent reply other threads:[~2007-12-10 8:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 16:01 [gentoo-dev] [GLEP] scm package version suffix Piotr Jaroszyński
2007-12-09 16:18 ` Josh Sled
2007-12-09 17:22 ` Piotr Jaroszyński
2007-12-09 17:52 ` Petteri Räty
2007-12-09 18:00 ` Piotr Jaroszyński
2007-12-09 18:45 ` Jan Kundrát
2007-12-09 18:57 ` Ciaran McCreesh
2007-12-10 4:31 ` Donnie Berkholz
2007-12-10 7:18 ` Ciaran McCreesh
2007-12-10 7:44 ` Nirbheek Chauhan
2007-12-10 8:24 ` Ciaran McCreesh
2007-12-10 8:36 ` Robin H. Johnson
2007-12-10 8:44 ` Ciaran McCreesh
2007-12-11 1:12 ` [gentoo-dev] " Ryan Hill
2007-12-10 12:59 ` [gentoo-dev] " Robert Buchholz
2007-12-10 14:24 ` Nirbheek Chauhan
2007-12-10 15:14 ` Robert Buchholz
2007-12-10 19:44 ` Nirbheek Chauhan
2007-12-10 19:49 ` Nirbheek Chauhan
2007-12-11 0:27 ` [gentoo-dev] " Steve Long
2007-12-11 10:59 ` Nirbheek Chauhan
2007-12-11 11:03 ` Nirbheek Chauhan
2007-12-11 8:21 ` Duncan
2007-12-11 11:06 ` Nirbheek Chauhan
2007-12-11 11:17 ` Ciaran McCreesh
2007-12-11 12:10 ` Nirbheek Chauhan
2007-12-10 8:26 ` Robin H. Johnson [this message]
2007-12-10 8:34 ` [gentoo-dev] " Ciaran McCreesh
2007-12-10 9:21 ` [gentoo-dev] Handling branch strings Donnie Berkholz
2007-12-10 9:34 ` Santiago M. Mola
2007-12-10 19:42 ` Donnie Berkholz
2007-12-11 1:35 ` [gentoo-dev] " Ryan Hill
2007-12-11 8:11 ` [gentoo-dev] " Ciaran McCreesh
2007-12-11 11:46 ` Santiago M. Mola
2007-12-11 17:56 ` [gentoo-dev] " Christian Faulhammer
2007-12-09 19:38 ` [gentoo-dev] Re: [GLEP] scm package version suffix Ryan Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071210082621.GF14557@curie-int.orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox