public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Dirt: To shove under the rug or not shove under the rug? (aka another round of USE_EXPAND)
Date: Tue, 27 Sep 2005 11:48:01 -0500	[thread overview]
Message-ID: <20050927164801.GB30337@nightcrawler> (raw)
In-Reply-To: <843E5A1C-7514-4E4F-891B-999E57CA8D0C@gentoo.org>

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

On Tue, Sep 27, 2005 at 09:07:00AM -0500, Kito wrote:
> [Portage devs please don't throw rocks at me]
All out of rocks :/

> My impression of the userland, elibc, and kernel use expanded vars is  
> it was a quick way to sidestep some of the issues with GLEP22... it  
> would seem the full keywords have still not been taken advantage of.  
> From the ebuild perspective, if the profile has a keyword of x86- 
> fbsd-bsd-fbsd, there is no clean way to just do a conditional based  
> on a 'Keyword Fragment' as there are obviously namespace collisions.
> 
> Ideal to me would be syntax something like:
> 
>   kernel !fbsd && foo
>   libc glibc || bar
>   userland darwin && boof

Bash side of it's pretty easy to implement however needed, the problem 
here (and why imo USE_EXPAND came into existance) is getting those 
conditional nodes into the dep syntax evaluation without trampling 
other use vars.

And *-*-*-fbsd as a conditional node sucks in depends, is ugly, oh so 
ugly.  :)
~harring

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

  parent reply	other threads:[~2005-09-27 16:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27  9:23 [gentoo-dev] Dirt: To shove under the rug or not shove under the rug? (aka another round of USE_EXPAND) Jason Stubbs
2005-09-27  9:38 ` Diego 'Flameeyes' Pettenò
2005-09-27 10:12   ` Jason Stubbs
2005-09-27 10:41     ` Diego 'Flameeyes' Pettenò
2005-09-27 12:51       ` Jason Stubbs
2005-09-27 13:44         ` Diego 'Flameeyes' Pettenò
2005-09-27 14:07           ` Kito
2005-09-27 16:27             ` Stephen Bennett
2005-09-27 16:48             ` Brian Harring [this message]
2005-09-27 14:25           ` Jason Stubbs
2005-09-27 15:40       ` [gentoo-dev] " Duncan
2005-09-27 12:38     ` [gentoo-dev] " Chris Gianelloni
2005-09-27 15:36       ` Donnie Berkholz
2005-09-27 10:54 ` Thomas de Grenier de Latour
2005-09-27 12:31   ` Jason Stubbs
2005-09-27 12:35 ` Chris Gianelloni
2005-09-27 13:07   ` Thomas de Grenier de Latour
2005-09-27 13:50     ` Chris Gianelloni
2005-09-27 14:20   ` Jason Stubbs
2005-09-27 15:35 ` Donnie Berkholz
2005-09-28  1:23   ` Jason Stubbs
2005-09-28  3:13     ` Jason Stubbs
2005-09-28  3:58   ` Jason Stubbs
2005-09-28  4:19     ` Donnie Berkholz
2005-09-28  4:45       ` Jason Stubbs
2005-09-28  6:23         ` Donnie Berkholz
2005-09-28  8:03           ` Jason Stubbs
2005-09-28  4:21     ` Jason Stubbs

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=20050927164801.GB30337@nightcrawler \
    --to=ferringb@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