1 |
To repeat and extend what I said: |
2 |
|
3 |
On Sunday 23 December 2001 16:13, you wrote: |
4 |
> > > 1. If the FHS say only binary stuff goes in /opt, where would I put |
5 |
> > > several KDEs-in-testing? /usr/kde-$ver? |
6 |
> > |
7 |
> > Whatever makes sense; just don't use /opt. |
8 |
|
9 |
On that subject, I'd like to raise once more the issue of KDE placing. Now |
10 |
is the last time we can easily change it, before doing kde3 ebuilds. I |
11 |
still think there should be support for multiple KDEs, which would live in |
12 |
e.g. /usr/kde-$ver each. Juggling paths would be a lot easier. |
13 |
|
14 |
The way things work right now - one big kde in /usr, many kdelibs in |
15 |
/usr/lib/kdelibs-$ver - there are the following problems, which will |
16 |
disappear if we place all KDEs (incl. kdelibs) in /usr/kde-$ver and put each |
17 |
app in the dir of the kdelibs to which it links: |
18 |
|
19 |
- Many users will want multiple KDEs, with or without ebuilds that support |
20 |
it. It'd be better for us to do it for them, so that things are unified. |
21 |
|
22 |
- Some apps don't like living separately from their kdelibs. In particular, |
23 |
noatun doesn't work at all (and apparently is unfixable save by patching the |
24 |
code or moving lots of files around), mosfet's liquid widgets require a |
25 |
makefile patch (applied), and kdm can't find the user icons (one possible |
26 |
solution is to manually move the icons in src_install). Other problems will |
27 |
likely arise. |
28 |
|
29 |
- With one kde in /usr, it can be (from expirience) very complicated to |
30 |
startup a kde that lives elsewhere, since /usr always commes first in the |
31 |
paths. |
32 |
|
33 |
- eclasses (and kdelibs & kdebase ebuilds) are becoming more and more complex |
34 |
and tangled to support all this. |
35 |
|
36 |
I don't know how FHS-compatible that is (i.e. /usr/kde-$ver), beyond not |
37 |
putting kde in /opt. But I'd really like it to be that way - it would |
38 |
certainly make everybody's life easier. |
39 |
|
40 |
Now, I unfortunately missed the orig. kde->/usr thread back when it was |
41 |
discussed. Apparently it was mostly on IRC and not on the mailing lists so |
42 |
the only reason for having kde in /usr I really know is the FHS. There may be |
43 |
other & better reasons. |
44 |
|
45 |
Even if we decide to hav only 1 kde, it will still be a lot better no to ahve |
46 |
in /kde. If we have /usr/kde-$ver dirs, each of which will contain a |
47 |
kdelibs-$ver and all apps linked against it, and kde base will live in one of |
48 |
those, it'll be a lot better than it is now. Again, because the kde that |
49 |
lives in /usr has execution priority over any others. |
50 |
|
51 |
What all this cimes to is that if we make kde live in /usr, we won't be able |
52 |
to support multiple kdes, and it will be difficult for users to set up |
53 |
mltiple kdes on their own. |
54 |
|
55 |
-- |
56 |
|
57 |
Dan Armak |
58 |
Gentoo Linux Developer, Desktop Team |
59 |
Matan, Israel |