public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rémi Cardona" <remi@gentoo.org>
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 08:04:18 +0200	[thread overview]
Message-ID: <48E06FE2.3010403@gentoo.org> (raw)
In-Reply-To: <48DECDFE.7010606@gentoo.org>

Zac Medico a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi everyone,
>
> Please consider a PROPERTIES=set value that allows an ebuild to
> indicate that it should behave like a package set when selected on
> the command line. This is behavior is somewhat difficult to describe
> in words but the following example should be sufficient to convey
> the general idea.

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) ?

The one thing that bothers me about this is consistency: if, say, xfce 
(let's change ;) ) decides to use PROPERTIES=set, users will have a 
different experience with their ebuild than with the other metas we 
currently ship.

All in all, I'm not really against such a change, however I really fail 
to see the win for everyone, end-users included.

Cheers :)

Rémi



  parent reply	other threads:[~2008-09-29  6:05 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 ` Rémi Cardona [this message]
2008-09-29  6:33   ` [gentoo-dev] " 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=48E06FE2.3010403@gentoo.org \
    --to=remi@gentoo.org \
    --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