From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
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 00:02:57 +0100 [thread overview]
Message-ID: <20080929000257.7bfd0905@snowmobile> (raw)
In-Reply-To: <48E00B9B.3060600@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
On Sun, 28 Sep 2008 15:56:27 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> As I've tried to explain, the an ebuild which exhibits
> PROPERTIES=set doesn't necessarily have to behave any differently
> than a meta-package currently does. What we would do is create a
> configuration that maps the set-property ebuild into set space. For
> example, `emerge kde-meta` would behave as as normal meta-package
> currently does, and `emerge @kde-meta` would reference the same
> package as a set and could thereby trigger different behavior which
> is appropriate for a set.
...and what would that behaviour be? What does a PDEPEND mean for a
set?
> > Here's an alternate proposal: Repositories can ship sets via files
> > in sets/*.conf. The format is as described in [1]. In configuration
> > files, operations applied to a set are applied to anything matching
> > any spec listed in that set (or any set that set contains, and so
> > on). On the command line, sets and non-sets cannot be mixed, and
> > multiple sets cannot be specified.
> >
> > [1]: http://paludis.pioto.org/configuration/sets.html
> >
>
> Perhaps can use something like you've got there in addition to the
> PROPERTIES=set approach.
Why the need for multiple solutions at all? PROPERTIES=set is too weird
and involves too much nonsensical behaviour to be useful.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-28 23:03 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 [this message]
2008-09-28 23:37 ` Zac Medico
2008-09-29 15:13 ` Bo Ørsted Andresen
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=20080929000257.7bfd0905@snowmobile \
--to=ciaran.mccreesh@googlemail.com \
--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