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