From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Handling branch strings
Date: Mon, 10 Dec 2007 19:35:37 -0600 [thread overview]
Message-ID: <fjkphb$s27$1@ger.gmane.org> (raw)
In-Reply-To: <20071210194238.GC31432@supernova>
Donnie Berkholz wrote:
> On 10:34 Mon 10 Dec , Santiago M. Mola wrote:
>> On Dec 10, 2007 10:21 AM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
>>> While we're getting a bit off the original topic here, it occurred to me
>>> that using SLOTs for this, in combination with various SLOT deps and
>>> SLOT blockers, might work. Then one could use a search tool that would
>>> display SLOTs to show you which branch you're getting.
>> Too tricky. It would confuse package managers and would break the
>> meaning of SLOT. An use expanded SCM_BRANCH combined with use
>> dependencies makes more sense and, hopefully, would be something
>> manageable.
> You've made these assertions about confusion and breakage, and I would
> like to understand the reasoning behind them. I don't understand how it
> would be different than any other SLOT, because they're already a
> string. USE_EXPAND doesn't allow for the possibility of multiple SLOTs
> installed at once, which is a feature I would like.
Right, can't you just suffix the SLOT name? My gcc svn builds just
do SLOT="${GCC_BRANCH_VER}-svn". This could be a special case though
since a gcc install is pretty carefully separated from its other SLOTs.
--
looks like christmas at fifty-five degrees
this latitude weakens my knees
EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 (0xF9A40662)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-12-11 1:38 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 ` [gentoo-dev] " Robin H. Johnson
2007-12-10 8:34 ` 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 ` Ryan Hill [this message]
2007-12-11 8:11 ` 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='fjkphb$s27$1@ger.gmane.org' \
--to=dirtyepic@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