[pkg-kde-talk] Re: kdelibs4c2a <-> kdelibs-bin circular dependency - advice requested

[Pierre Habouzit]

Le Ven 20 Janvier 2006 23:17, Bill Allombert a écrit :
> Alternatively, you can fix the co-installability problem by
> versioning the path to the binaries, e.g. moving them to
> /usr/lib/kdelibs4/ and make sure the libraries use the correct path.

honnestly, there is no point in doing that. This would make the 
packaging even more painfull that it is now, with almost no gain.

The only way to achieve reall co-instability is to do as gentoo does : 
make KDE live in /usr/kde/x.y/ which would be a major policy violation, 
and which makes no sense at all.

your arguments about multiarch *are* valid and deserve some pondering 
(especially since users may want a 32bits konqueror to be able to use 
macromedia flash plugin, or sun's java plugin...). but honnestly, 
beeing able to co-install different kdelibs *versions* has no point at 
all, since no one would really take advantage of this.


In the KDE world, most applications migrate to the new kdelibs/kdebase 
with each new KDE release. I've really problems to think of a situation 
where co-instability would really help any user. Moreover, it's not 
really a feature that our users want. Developpers have their own 
checkout of kde-HEAD in their home, and adjust their KDE_PATH to 
$HOME/kde-head/ and the trick is done, they have two version of KDE on 
the same system.


-- 
·O·  Pierre Habouzit
··O                                                madcoder at debian.org
OOO                                                http://www.madism.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20060120/819cc103/attachment.pgp