public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: [RFC] PROPERTIES=virtual for meta-packages (clarification of definition)
Date: Tue, 26 Aug 2008 14:20:44 +0100	[thread overview]
Message-ID: <20080826142044.28367055@googlemail.com> (raw)
In-Reply-To: <pan.2008.08.26.06.39.38@cox.net>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

On Tue, 26 Aug 2008 06:39:38 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
> But I think virtual works just fine for kde-base/kde, too, if one
> simply reads it literally -- it's a virtual package in that it
> doesn't install anything itself, even if it's a meta-package rather
> than having the meaning of the old-style virtual, that of selecting
> one of many providers.  So the only problem with virtual is the
> narrower old meaning.  Whether that's a big enough problem to worry
> about is of course debatable, but I don't personally believe it is,
> and find it every bit as clear and actually much less confusing than
> zero-install-cost.

So what does 'virtual' actually mean then, and how is it related to the
defined behaviour of this property?

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-08-26 13:20 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
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 [this message]
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=20080826142044.28367055@googlemail.com \
    --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