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: Dependencies that're available at pkg_*inst
Date: Sun, 27 Apr 2008 11:55:56 +0100	[thread overview]
Message-ID: <20080427115556.13667557@snowcone> (raw)
In-Reply-To: <fv1hqo$80m$1@ger.gmane.org>

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

On Sun, 27 Apr 2008 10:41:57 +0100
Steve Long <slong@rathaus.eclipse.co.uk> wrote:
> Use PDEPEND.

PDEPEND has a different meaning, and isn't suitable for runtime
dependencies.

> While I like labels they need to be discussed more on-list as well as
> on bugzilla (it's not reasonable for you simply to advertise them and
> then close down discussion.) For instance, there is no reason
> everything has to be loaded into just one extant metadatum, not do
> they preclude new metadata (such as a SRC_DEP here.)

Labels can be discussed on-list whenever there's a chance in hell of
Portage implementing any non-trivial new features.

Anyway, I'm going with the second wording in the original email. It
seems fairly clear that most people aren't understanding the issue, and
are jumping in and offering opinions without having looked at the tree
(and no, I'm not going to give examples, because that'll just
degenerate into "oh, so we can change this one particular case to do
$blah", whilst missing the bigger point). Of everything suggested, only
the two original wordings are correct, and of those two, the second is
better defined.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2008-04-27 10:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19  4:31 [gentoo-dev] Dependencies that're available at pkg_*inst Ciaran McCreesh
2008-04-19  4:45 ` Donnie Berkholz
2008-04-19  4:54   ` Ciaran McCreesh
2008-04-19  5:27     ` Donnie Berkholz
2008-04-19  5:33       ` Ciaran McCreesh
2008-04-19  7:43         ` Chris Gianelloni
2008-04-22  7:09           ` Ciaran McCreesh
2008-04-22 18:31             ` Chris Gianelloni
2008-04-19 18:53         ` [gentoo-dev] " Duncan
2008-04-19 23:55           ` Ciaran McCreesh
2008-04-21  5:17         ` [gentoo-dev] " Donnie Berkholz
2008-04-21  5:23           ` Ciaran McCreesh
2008-04-21  8:52             ` Marijn Schouten (hkBst)
2008-04-21  9:00               ` Ciaran McCreesh
2008-04-21 10:22           ` [gentoo-dev] " Duncan
2008-04-21 10:10         ` [gentoo-dev] " Luca Barbato
2008-04-21 10:15           ` Ciaran McCreesh
2008-04-21 10:05     ` Luca Barbato
2008-04-21 10:17       ` Arfrever Frehtes Taifersar Arahesis
2008-04-22 20:32     ` Doug Goldstein
2008-04-19 16:38 ` Marijn Schouten (hkBst)
2008-04-19 23:57   ` Ciaran McCreesh
2008-04-20  1:29     ` Brian Harring
2008-04-20  8:36       ` Ciaran McCreesh
2008-04-20 10:48         ` Santiago M. Mola
2008-04-22 20:31     ` Doug Goldstein
2008-04-27  9:41     ` [gentoo-dev] " Steve Long
2008-04-27 10:55       ` Ciaran McCreesh [this message]
2008-04-28  4:57         ` [gentoo-dev] " Steve Long
2008-04-28 12:13           ` Ciaran McCreesh

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=20080427115556.13667557@snowcone \
    --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