| 1 |
Petteri Räty wrote: |
| 2 |
|
| 3 |
>warnera6 wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>IMHO it is, but not as a USE flag (it will never be stable enough |
| 7 |
>>without upstream support) but I think many would find the functionality |
| 8 |
>>useful in a script. I know I would. If it works most of the time and |
| 9 |
>>saves space, there is no reason not trim things. If it breaks, you |
| 10 |
>>immediately revert to a normal build. |
| 11 |
>> |
| 12 |
>> |
| 13 |
>> |
| 14 |
> |
| 15 |
>Well this would not give the advantage of cutting down emerge times. Why |
| 16 |
>the script when you can just turn off the use flag? |
| 17 |
> |
| 18 |
> |
| 19 |
> |
| 20 |
Because the USE flag itself doesn't produce stable output and shouldn't |
| 21 |
be in a stable tree, IMHO. You can't mask use flags ~arch. |
| 22 |
|
| 23 |
>>>Or, put the kernel source on a cd, and build off of it (putting the |
| 24 |
>>>objects on your local disk.) This lets you only use the local disk for |
| 25 |
>>>your built objects. |
| 26 |
>>> |
| 27 |
>>> |
| 28 |
> |
| 29 |
>I can always maintain this in my overlay if I want to so that is no |
| 30 |
>problem. I just thought this might be useful for other people too. |
| 31 |
> |
| 32 |
>Regards, |
| 33 |
>Petteri Räty (Betelgeuse) |
| 34 |
> |
| 35 |
> |
| 36 |
> |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives