1 |
On Tue, Sep 27, 2005 at 09:07:00AM -0500, Kito wrote: |
2 |
> [Portage devs please don't throw rocks at me] |
3 |
All out of rocks :/ |
4 |
|
5 |
> My impression of the userland, elibc, and kernel use expanded vars is |
6 |
> it was a quick way to sidestep some of the issues with GLEP22... it |
7 |
> would seem the full keywords have still not been taken advantage of. |
8 |
> From the ebuild perspective, if the profile has a keyword of x86- |
9 |
> fbsd-bsd-fbsd, there is no clean way to just do a conditional based |
10 |
> on a 'Keyword Fragment' as there are obviously namespace collisions. |
11 |
> |
12 |
> Ideal to me would be syntax something like: |
13 |
> |
14 |
> kernel !fbsd && foo |
15 |
> libc glibc || bar |
16 |
> userland darwin && boof |
17 |
|
18 |
Bash side of it's pretty easy to implement however needed, the problem |
19 |
here (and why imo USE_EXPAND came into existance) is getting those |
20 |
conditional nodes into the dep syntax evaluation without trampling |
21 |
other use vars. |
22 |
|
23 |
And *-*-*-fbsd as a conditional node sucks in depends, is ugly, oh so |
24 |
ugly. :) |
25 |
~harring |