| 1 |
On 05/16/2010 06:26 PM, Bill Kenworthy wrote: |
| 2 |
> -t doesnt work in this case as emerge wants xorg-server built with the |
| 3 |
> kdrive flag before it will continue processing - which makes sense. |
| 4 |
|
| 5 |
AFAICT, the cost of enabling kdrive is trivial. It compiles one more |
| 6 |
"server" /usr/bin/Xephyr, so I'd say just enable kdrive and go for it! |
| 7 |
|
| 8 |
> |
| 9 |
> On Sun, 2010-05-16 at 15:55 -0700, walt wrote: |
| 10 |
>> On 05/15/2010 09:42 PM, William Kenworthy wrote: |
| 11 |
>>> I am trying to update a laptop after a break of a few months and have |
| 12 |
>>> an ... anomaly! |
| 13 |
>>> |
| 14 |
>>> It suddenly wants the kdrive use flag enabled for xorg-server and |
| 15 |
>>> sabayon - why? I think kdrive is a minimal xserver built on top of xorg |
| 16 |
>>> so its not appropriate for a system I want full functionality on - is |
| 17 |
>>> it? |
| 18 |
>>> |
| 19 |
>>> How can I find out whats bringing this use flag in as I cant find |
| 20 |
>>> anything so far. |
| 21 |
>> |
| 22 |
>> The method most often suggested is adding the 't' flag to your emerge: |
| 23 |
>> |
| 24 |
>> #emerge -auNDt world |
| 25 |
>> |
| 26 |
>> |
| 27 |
>> |
| 28 |
> |
| 29 |
> |
| 30 |
> |
Archives