From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: [RFC] PROPERTIES=set for meta-packages that should behave like package sets
Date: Mon, 29 Sep 2008 21:42:21 +0100 [thread overview]
Message-ID: <gbrf3u$7ps$1@ger.gmane.org> (raw)
In-Reply-To: 48E13A75.4010800@gentoo.org
Zac Medico wrote:
> Steve Long wrote:
>> Zac Medico wrote:
>>> Rémi Cardona wrote:
>>>> As one of the maintainers of the gnome-base/gnome meta, I fail to see
>>>> the usefulness of such a change. We have yet to ask users to rebuild
>>>> "gnome" completely. Do you have any specific use cases (maybe coming
>>>> from the KDE herd, since you used the kde meta as an example) ?
>>>>
>>> Over the course of the discussion I've revised the idea so that it
>>> essentially represents a way to define a package set, without any
>>> changes to existing behavior. What will change is that we will have
>>> a new way to define package sets, based on ebuilds.
>>
>> Makes sense to me, though not sure you need the mapping file. I'm
>> perfectly happy about emerge -uDN @kde-meta say, updating all kde-meta
>> packages I might have installed; I take it that after emerge kde-meta to
>> install, and then removing some of the packages, the user could continue
>> to reference the set for upgrade, without portage reinstalling those?
>
> That would be a set subtraction operation, so the user would use a
> configuration file to configure the set so that certain unwanted
> atoms are automatically subtracted out. Alternatively, we could
> implement a syntax extension for "optional atoms" that are only
> pulled into the dependency graph if they happen to be installed already.
>
It would be nice to address it; wrt people installing a meta which will
define a set, it'd make it easier to maintain (a box) if the set syntax
referred to whatever was installed, whereas emerging the package would
install all its deps as a standard virtual does (in the default setting.)
Integrating seems like a good idea, wrt to the USE settings you discussed in
the other thread. There is already a framework in place to model all that,
and more, so might as well use it. (I'd vote for allowing as much
flexibility as the ebuild author wants to specify.)
prev parent reply other threads:[~2008-09-29 20:51 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
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 ` Steve Long [this message]
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='gbrf3u$7ps$1@ger.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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