Re: [gentoo-dev] Handling branch strings
On Mon, 10 Dec 2007 11:42:38 -0800 Donnie Berkholz [EMAIL PROTECTED] wrote: 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. Conceptually a branch is not a slot (nor is it a version). Reusing an existing package manager concept for a second, unrelated concept leads to excessively complicated handling rules and a general nasty mess. If there's desire for the package manager to be aware of branches, it should be a separate proposal using a concept specifically designed for that purpose. Branches exist without SCM, and SCM exists without branches, and neither have anything to do with slots or use flags. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] Handling branch strings
On Dec 11, 2007 9:11 AM, Ciaran McCreesh [EMAIL PROTECTED] wrote: On Mon, 10 Dec 2007 11:42:38 -0800 Donnie Berkholz [EMAIL PROTECTED] wrote: You've made these assertions about confusion and breakage, and I would like to understand the reasoning behind them. [...] For my reasoning... just read Ciaran's reply ;-) -- Santiago M. Mola Jabber ID: [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Handling branch strings
On 00:26 Mon 10 Dec , Robin H. Johnson wrote:
What I've got for my Xorg testing setup, is foo--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.
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.
Thanks,
Donnie
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Handling branch strings
On Dec 10, 2007 10:21 AM, Donnie Berkholz [EMAIL PROTECTED] wrote:
On 00:26 Mon 10 Dec , Robin H. Johnson wrote:
What I've got for my Xorg testing setup, is foo--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.
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.
Regards,
Santiago
--
Santiago M. Mola
Jabber ID: [EMAIL PROTECTED]
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Handling branch strings
On 10:34 Mon 10 Dec , Santiago M. Mola wrote:
On Dec 10, 2007 10:21 AM, Donnie Berkholz [EMAIL PROTECTED] wrote:
On 00:26 Mon 10 Dec , Robin H. Johnson wrote:
What I've got for my Xorg testing setup, is foo--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.
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.
Thanks,
Donnie
--
[EMAIL PROTECTED] mailing list
