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: Mon, 8 Sep 2008 23:07:18 +0100 [thread overview]
Message-ID: <20080908230718.5bcb665d@snowmobile> (raw)
In-Reply-To: <ga46f5$4kj$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Mon, 08 Sep 2008 22:40:37 +0100
Steve Long <slong@rathaus.eclipse.co.uk> wrote:
> >> * should be treated as being very quickly installable
> >> * should be treated as having zero cost for installs
> >>
> Both of which follow from "installs nothing." Or would you disagree?
No, they're separate properties, with different implications.
Consider, for example, a split baselayout-style package. There could be
a skeleton-filesystem-layout package that does all its work in pkg_*
functions (to avoid permission and empty directory problems that come
from installing directories via the normal methods). It would install
nothing, but should not be considered for either zero-cost property.
Or, for the reverse: a package that merely installs a simple control
file that enables functionality in another package may well be best
considered as zero-cost for package selection. If a package depends
upon || ( big-scary/processing-package simple-little/plugin-for-foo )
and you already have foo but not plugin-for-foo installed, the right
thing for the resolver to do would be to suggest plugin-for-foo.
As for the quickly installable property, plugin-for-foo might not
possess it -- for example, vim plugins generally do a vim tag
regeneration upon pkg_postinst, so they're not 'quick' to install even
if all they do is provide one text file.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-08 22:07 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
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 [this message]
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=20080908230718.5bcb665d@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