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] Dependencies that're available at pkg_*inst
Date: Sun, 20 Apr 2008 09:36:13 +0100	[thread overview]
Message-ID: <20080420093613.1122a705@snowcone> (raw)
In-Reply-To: <20080420012910.GA8373@seldon.hsd1.ca.comcast.net>

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

On Sat, 19 Apr 2008 18:29:10 -0700
Brian Harring <ferringb@gmail.com> wrote:
> Not all cycles are solvable w/in the domain of execution which is an 
> unfortunate fact.  This loops back into why jstubbs was after use dep 
> cycle breaking (fair bit more fine grained of an issue), a discussion 
> that thus far has been ignored, and the usage of the build flag.

Which, again, is a future thing, since it requires additional per-ebuild
information about how use flags are used to be implementable.

> Stop name dropping labels until you tell folk about what labels are.  
> I know, but I'd rather not have the notion "labels solves all" pushed 
> forth w/ out people knowing what it is, please.

Labels are already documented and discussable in the appropriate place.
This is not supposed to be a discussion about future direction. It's
supposed to be about one specific issue regarding how we word things for
current implementations. The two wordings in the original email do not
have equivalent implications, and selecting the correct one affects
whether certain problems are solvable. Let's discuss that, not what
we're going to do six years from now.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2008-04-20  8:36 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 [this message]
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
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=20080420093613.1122a705@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