1 |
Jan Kundrát wrote: |
2 |
> Jorge Manuel B. S. Vicetto wrote: |
3 |
>> Some members of the KDE team have been talking for some time about |
4 |
>> having a FHS compliant install (define KDE prefix as /usr instead of |
5 |
>> /usr/kde/<version>). |
6 |
> What are benefits of such a change? What happens when KDE release a |
7 |
> version breaking ABI (like "KDE 5")? |
8 |
We would have the option of using a kde prefix in order to slot it with |
9 |
KDE 4, other distros have worked hard to actually slot KDE 3 and 4 |
10 |
installed in /usr/ this time around. Ideally we would work with them to |
11 |
achieve a similar outcome. We would certainly still have options if and |
12 |
when this happens, i.e. using an alternate prefix so that they can be |
13 |
slotted or truly slotting the two in /usr. |
14 |
> |
15 |
> Right now [1], there's a conflict between some non-kdelibs kde3 |
16 |
> libraries (kexiv2, kdcraw) from KDE3 and KDE4, mainly KDE4 |
17 |
> applications being linked with KDE3 libraries. I don't expect ABI |
18 |
> breakage in 4.x, but what happens after it? |
19 |
kexiv2 etc are effectively KDE libraries that have recently moved to be |
20 |
developed in KDE's repository. We were discussing whether they should |
21 |
continue to be bumped in the media-libs category or not. This is a |
22 |
recent move and they are certainly not core libs. I haven't checked yet |
23 |
but I am not sure whether they break API or not. |
24 |
> |
25 |
> Will I be able to use my desktop in the middle of an upgrade from 4.x |
26 |
> to 4.(x+1), when only half of the packages are already updated? |
27 |
The KDE apps should just link to the latest kdelibs, KDE guarantees ABI |
28 |
stability and so this should be an easy process. It is possible this |
29 |
will not always be as smooth as we would like with libkdeedu etc. Can |
30 |
Gnome guarantee that everything will continue to work at all stages of |
31 |
the upgrade too? I am not sure how I can effectively test that and make |
32 |
a promise but from my experience as long as we upgrade the libs first |
33 |
and the apps second everything will work well. |
34 |
>> In case someone is thinking on suggesting it, ignoring FHS or not |
35 |
>> allowing the install of multiple versions are not valid solutions to |
36 |
>> this problem. |
37 |
> |
38 |
> I might have missed something in your mail, but if you put, say, 4.1 |
39 |
> and 4.2 libraries straight into /usr/lib, are you completely positive |
40 |
> stuff won't break |
41 |
So long as things are upgraded libraries first, then applications (as |
42 |
specified by the deps) then this should not cause any issues. Although |
43 |
we will continue having KDE 4.2 applications depend on >= 4.2. |