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: Sun, 28 Sep 2008 22:01:51 +0100 [thread overview]
Message-ID: <20080928220151.33656aca@snowmobile> (raw)
In-Reply-To: <48DFEEB8.5040608@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
On Sun, 28 Sep 2008 13:53:12 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> >> Does this seem like a good approach? Are there any suggestions for
> >> improvements or alternative approaches?
> >
> > Strikes me as a good way of causing extreme confusion for users...
>
> Perhaps it's not so confusing if the packages continue to behave
> normally in the usual cases, but they are mapped into set space as
> suggested earlier [1].
Then why not just make the things sets? Come up with a standard way of
distributing sets as part of a repository, and let future EAPIs include
deps upon sets.
> > Consider sets in package.use, for example. Any specified flags
> > should apply to the entire set. But what about set-property
> > packages?
>
> In order to fit into the ebuild framework, the specified flags would
> only apply to direct dependency atoms. Atoms pulled in by recursion
> into other set-property packages would have the flags applied from
> those respective set-property packages.
Right, so you'd get the bizarre case that, given:
cat/foo one
cat/bar two
cat/baz three
The one flag applies onto to cat/foo, the three flag applies only to
cat/baz but the two flag applies to cat/monkey and cat/hamster.
Sets need to *look* different...
> > Sets and packages aren't the same thing, and shouldn't be treated
> > as if they are.
>
> Packages and virtuals aren't the same thing either, but glep 37
> virtuals fit quite well into the existing ebuild framework. It seems
> to me that set-property packages will also fit nicely into the
> existing ebuild framework.
GLEP 37 effectively abolishes virtuals. It doesn't try to overload new
behaviour onto packages.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-28 21:02 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 [this message]
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
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=20080928220151.33656aca@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