1 |
On Thursday 20 October 2005 09:11, Donnie Berkholz wrote: |
2 |
> Metabuilds should be forthcoming shortly. I'd appreciate input on |
3 |
> http://dev.gentoo.org/~spyderous/xorg-x11/metabuilds.txt and in |
4 |
> particular from people on the GNOME and KDE teams. |
5 |
|
6 |
KDE doesn't have any special requirements. It doesn't use any kind of X11 |
7 |
build tool (what is there other than imake?). It does use some X apps like |
8 |
xmessage, xset etc. After you commit your metaebuilds we'll update the deps |
9 |
as needed. The only metaebuild we'll need to depend on is -libs. |
10 |
|
11 |
However, consider this usecase: user (who's used to the old docs) installs new |
12 |
stage3, types 'emerge kde', runs kdm... oops, no X server... |
13 |
|
14 |
To keep the current behaviour, the kde metaebuild (and gnome and the other |
15 |
WMs) would have to depend on xorg-x11, which strictly speaking is |
16 |
unnecessary. Opinions? How can we educate the users to manually 'emerge |
17 |
xorg-x11'? Personally I'm in favor of updating the docs, making a big |
18 |
announcement on all channels, and preparing a nice bug to close duplicates |
19 |
against. |
20 |
|
21 |
We'll also need to educate them about xorg-x11 not installing fonts any |
22 |
longer. The way I understood your metabuilds.txt, 'emerge xorg-x11 kde' would |
23 |
result in an unusable system without any fonts at all... |
24 |
|
25 |
-- |
26 |
Dan Armak |
27 |
Gentoo Linux developer (KDE) |
28 |
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key |
29 |
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951 |