public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] PROPERTIES=virtual for meta-packages (clarification of definition)
Date: Mon, 25 Aug 2008 12:36:34 -0700	[thread overview]
Message-ID: <48B309C2.1060204@gentoo.org> (raw)
In-Reply-To: <20080825201217.194fecad@googlemail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ciaran McCreesh wrote:
> On Mon, 25 Aug 2008 12:06:35 -0700
> Zac Medico <zmedico@gentoo.org> wrote:
>> Ciaran McCreesh wrote:
>>> So are all zero-install-cost metapackages virtuals now? What about,
>>> for instance, kde-base/kde?
>> Looking at the dependencies of kde-base/kde, it seems like it would
>> be eligible to exhibit the "virtual" property. Perhaps it wouldn't
>> be very useful in this particular case, but it doesn't seem like it
>> would hurt anything either. So, I think it's probably fine to keep
>> the definition as it is and allow things like kde-base/kde to
>> exhibit the "virtual" property.
> 
> Then change the name. Call it "zero-install-cost".

I'm inclined toward "virtual" since it's more brief and I think it
might strike a chord with more people because of their familiarity
with the "virtual" category and old-style PROVIDE virtuals. We'll
have to see what others have to say.
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkizCcAACgkQ/ejvha5XGaO2WQCcCtL56YFoyBxNz5XUvPuJ/EMq
GQsAoMLMDEk1Yd9N86SQUM1A92hntjFE
=hwz3
-----END PGP SIGNATURE-----



  reply	other threads:[~2008-08-25 19:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 21:01 [gentoo-dev] [RFC] PROPERTIES=virtual for meta-packages (clarification of definition) Zac Medico
2008-08-25 17:51 ` Michal Kurgan
2008-08-25 18:01   ` Zac Medico
2008-08-25 18:37     ` Michal Kurgan
2008-08-25 18:40 ` Ciaran McCreesh
2008-08-25 19:06   ` Zac Medico
2008-08-25 19:12     ` Ciaran McCreesh
2008-08-25 19:36       ` Zac Medico [this message]
2008-08-25 19:58         ` Joe Peterson
2008-08-25 20:03         ` David Leverton
2008-08-26  6:39           ` [gentoo-dev] " Duncan
2008-08-26 13:20             ` Ciaran McCreesh
2008-08-26 14:20               ` Duncan
2008-08-26 17:44                 ` Zac Medico
2008-08-27  0:08                   ` Duncan
2008-08-27  1:49                     ` Zac Medico
2008-08-27  2:23                       ` Michal Kurgan
2008-08-27  3:16                         ` Zac Medico
2008-08-27  4:18                           ` Zac Medico
2008-08-27  3:51                     ` Jorge Manuel B. S. Vicetto
2008-08-30  9:59                 ` Steve Long
2008-08-30 12:23                   ` Ciaran McCreesh
2008-08-31  2:29                     ` [gentoo-dev] " Steve Long
2008-08-31 12:30                       ` Ciaran McCreesh
2008-08-31 19:10                     ` [gentoo-dev] " Joe Peterson
2008-08-31 21:54                       ` Duncan
2008-09-05 13:50                 ` Marius Mauch
2008-09-05 13:44 ` [gentoo-dev] " Marius Mauch
2008-09-05 15:38   ` Joe Peterson
2008-09-05 15:46     ` Ciaran McCreesh
2008-09-05 15:50       ` Joe Peterson
2008-09-08 21:40         ` [gentoo-dev] " Steve Long
2008-09-08 22:07           ` Ciaran McCreesh
2008-09-10  1:30             ` [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=48B309C2.1060204@gentoo.org \
    --to=zmedico@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