| 1 |
Roy Marples wrote: |
| 2 |
> On Friday 09 June 2006 23:34, Mike Frysinger wrote: |
| 3 |
> |
| 4 |
>>On Friday 09 June 2006 16:35, Chris Gianelloni wrote: |
| 5 |
>> |
| 6 |
>>>This is the "official" (hehe) request for comments on making a policy of |
| 7 |
>>>how to handle ebuilds than can be used for either client or server and |
| 8 |
>>>how to allow for building client-only. |
| 9 |
>> |
| 10 |
>>rather than moving to some sort of policy that satisfies no one completely |
| 11 |
>>and we'll have to back out of later, why dont we wait until portage can |
| 12 |
>>give us proper support for USE=client/server |
| 13 |
>>-mike |
| 14 |
> |
| 15 |
> |
| 16 |
> So we have two use flags - client and server. Here are the possabilities |
| 17 |
> |
| 18 |
> -client -server |
| 19 |
> +client -server |
| 20 |
> +client +server |
| 21 |
> -client +server |
| 22 |
> |
| 23 |
> Do we read -client -server and +client +server to mean the same thing? |
| 24 |
> If so the logic can read |
| 25 |
> |
| 26 |
> if use client || ! use server ; then |
| 27 |
> # build client |
| 28 |
> fi |
| 29 |
> if use server || ! use client ; then |
| 30 |
> # build server |
| 31 |
> fi |
| 32 |
> |
| 33 |
> How does portage stop us from doing that now? |
| 34 |
> |
| 35 |
|
| 36 |
built_with_use is then incorrect, since for -client -server you really |
| 37 |
built both. |
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives