public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: [GLEP] scm package version suffix
Date: Tue, 11 Dec 2007 08:21:56 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.12.11.08.21.56@cox.net> (raw)
In-Reply-To: 8b4c83ad0712101144x19e75accm7845221977a6a73f@mail.gmail.com

"Nirbheek Chauhan" <nirbheek.chauhan@gmail.com> posted
8b4c83ad0712101144x19e75accm7845221977a6a73f@mail.gmail.com, excerpted
below, on  Tue, 11 Dec 2007 01:14:06 +0530:

> On Dec 10, 2007 8:44 PM, Robert Buchholz <rbu@gentoo.org> wrote:
>> That would still mean everything relies on n ebuilds with mutual
>> blocks. Even if that would work and it block upgrades, it is still not
>> a solution in terms of how to display a list of ebuilds in one tree in
>> an ordered list.
> 
> The mutual blocks can be via the very nature of the name of the ebuild
> (ie, the scm_bbranch), and not via unmaintainable dep blocks in the
> ebuilds.

But what about when there's a dependency on any of several branches?  
That gets hard to maintain if there are multiple ebuilds with similar 
dependencies.

However, that's where virtuals come in.  Create a single virtual, depend 
on it, and you have a single dependency instead of a whole complex list 
to maintain in all the various depending ebuilds.  Another alternative of 
course is an eclass, inherited by whatever otherwise depending ebuilds, 
that manages all the dependencies and blockages all in one spot.

Which just means there are existing solutions for that angle, so it's out 
of scope for this GLEP.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2007-12-11  8:25 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 [this message]
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                 ` [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=pan.2007.12.11.08.21.56@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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