| 1 |
> If I have the X-Flag set, which is okay because I want X, and try to emerge |
| 2 |
> jed to have a good editor, Gentoo wants to compile the whole XFree-Package to |
| 3 |
> also get xjed which I didn't want. |
| 4 |
|
| 5 |
Having X in USE does not mean that you want to compile X itself, it |
| 6 |
means that you want packages with _optional_ X functionality to be |
| 7 |
compiled with X support. So, having X in USE meant that you did want |
| 8 |
xjed to be built. |
| 9 |
|
| 10 |
> It compiles X with all drivers - Sorcerer Linux asked, which X11-drivers are |
| 11 |
> needed. |
| 12 |
> Same with alsa - all card-drivers are made, I have to edit the ebuild-file and |
| 13 |
> all changes will be gone after the next emerge rsync. |
| 14 |
|
| 15 |
Well, Gentoo and Sorcerer have different philosophies there. The Gentoo |
| 16 |
Linux philosophy is that it should be possible to build the entire |
| 17 |
system, as desired, without ever asking the user. I believe that an |
| 18 |
environment variable ALSA_CARDS can be set to control which cards |
| 19 |
are built with alsa-0.9. We should have that in the 0.5 series, too, |
| 20 |
but nobody has gotten around to it. As for building X modules, we |
| 21 |
should have a similar mechanism, you're quite right. If you post |
| 22 |
an "enhancement" bug about this at bugs.gentoo.org you'll maximize |
| 23 |
the chance of this happening in a reasonable amount of time. |
| 24 |
|
| 25 |
> As you see with XMMS and the complainments about the avi-plugin, especially |
| 26 |
> the Gentoo-user wants to have the power to control what is compiled and |
| 27 |
> installed. |
| 28 |
|
| 29 |
I do know that one of our devs was working on this problem yesterday. |
| 30 |
|
| 31 |
> And if I correctly understand the webpage then this is what Gentoo wants to |
| 32 |
> provide - but IMHO it doesn't at the moment. |
| 33 |
|
| 34 |
Fair enough. Care to help? We gratefully accept any help we can get. |
| 35 |
|
| 36 |
Thanks, |
| 37 |
g2boojum |
Archives