public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] PROPERTIES=set for meta-packages that should behave like package sets
Date: Mon, 29 Sep 2008 17:13:27 +0200	[thread overview]
Message-ID: <200809291713.30783.bo.andresen@zlin.dk> (raw)
In-Reply-To: <48E0151F.1020404@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

On Monday 29 September 2008 01:37:03 Zac Medico wrote:
> > Why the need for multiple solutions at all? PROPERTIES=set is too weird
> > and involves too much nonsensical behaviour to be useful.
>
> I don't see the PROPERTIES=set approach as being worse than any
> other approach for package set definition. It has lots of advantages
> because of the way that it fits into the existing ebuild framework
> like virtual ebuilds do [1], allowing it to leverage all of the
> existing features of the framework (including package.use) and also
> allowing it to leverage the tools that have been designed to work
> with the framework.
>
> [1] http://www.gentoo.org/proj/en/glep/glep-0037.html

I really don't see the advantages of fitting 'into the existing ebuild 
framework like virtual ebuilds do'. Can you name any real advantages to it? 
Having virtuals as ebuilds makes sense because ebuilds need to depend upon 
them. But I can see no decent use case for letting a non-set ebuild depend 
upon a set. As far as I'm concerned sets are merely a convenience for users. 
It allows them to install, reinstall (mostly of interest for scm ebuilds), 
keyword, unmask, set use flags for or uninstall a set of packages.

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-09-29 15:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28  0:21 [gentoo-dev] [RFC] PROPERTIES=set for meta-packages that should behave like package sets Zac Medico
2008-09-28 15:24 ` Marius Mauch
2008-09-28 17:42   ` Zac Medico
2008-09-28 20:26     ` Ciaran McCreesh
2008-09-28 20:44       ` Zac Medico
2008-09-28 20:32 ` Ciaran McCreesh
2008-09-28 20:53   ` Zac Medico
2008-09-28 21:01     ` Ciaran McCreesh
2008-09-28 22:11       ` Zac Medico
2008-09-28 22:28         ` Ciaran McCreesh
2008-09-28 22:56           ` Zac Medico
2008-09-28 23:02             ` Ciaran McCreesh
2008-09-28 23:37               ` Zac Medico
2008-09-29 15:13                 ` Bo Ørsted Andresen [this message]
2008-09-29 19:52                   ` Zac Medico
2008-09-30  4:47                     ` Jorge Manuel B. S. Vicetto
2008-09-30  5:31                       ` Zac Medico
2008-10-01  4:35                         ` [gentoo-dev] " Ryan Hill
2008-10-01 16:37                           ` Zac Medico
2008-10-02  2:51                             ` Jorge Manuel B. S. Vicetto
2008-10-04  6:05                               ` Ryan Hill
2008-10-04  6:42                                 ` Ryan Hill
2008-10-04 17:17                                   ` Zac Medico
2008-10-05 17:55                                     ` Ryan Hill
2008-10-13  2:11                                       ` Steve Long
2008-10-02 12:19                             ` Robert Bridge
2008-09-29  2:52             ` Duncan
2008-09-29  6:40               ` Zac Medico
2008-09-29 11:52                 ` Duncan
2008-09-29  6:04 ` [gentoo-dev] " Rémi Cardona
2008-09-29  6:33   ` Zac Medico
2008-09-29 19:52     ` [gentoo-dev] " Steve Long
2008-09-29 20:28       ` Zac Medico
2008-09-29 20:42         ` [gentoo-dev] " Steve Long

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=200809291713.30783.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --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