Re: KDE directory layout
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 04 November 2001 21:30, Ivan E. Moore II wrote:
> I'm also not going to even attempt to support that many kde configs. It's
> a bitch right now when I'm dealing with the stuff in testing and the stuff
> in sid...and the mixture of the two...imagine the issues that would be
> caused if people were mixing kde2 and kde3 stuff.
>
I didn't install any _application_ from kde 3 packages you did. The following
completely kills my kde 2.x installation although it seems that it shouldn't:
orion:exa$ sudo apt-get install -t unstable kdemultimedia-cvs-dev
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
artsbuilder-cvs kdelibs4 kdelibs4-dev libarts1 libarts1-dev libkmid0
libkmid0-dev libqt3-dev libqt3-mt-dev mpeglib-cvs noatun-cvs qt3-tools
The following packages will be REMOVED:
artsbuilder kde kdelibs-dev kdemultimedia-dev libarts-dev libarts-mpeglib
libkmid-dev libqt-dev mpeglib noatun uic
The following NEW packages will be installed:
artsbuilder-cvs kdelibs4 kdelibs4-dev kdemultimedia-cvs-dev libarts1
libarts1-dev libkmid0 libkmid0-dev libqt3-dev libqt3-mt-dev mpeglib-cvs
noatun-cvs qt3-tools
0 packages upgraded, 13 newly installed, 11 to remove and 883 not upgraded.
Need to get 9032kB/21.0MB of archives. After unpacking 53.0MB will be used.
Do you want to continue? [Y/n]
Net result: Many binaries crash until I remove the kde 3 cruft and remove and
reinstall kdelibs3. Why would you think it's happening? (No chance in
backtrace)
Suspect: libarts / mpeglib stuff.
Also needed: a kde-cvs-dev meta package would be handy. Let me see meta-kde
> And I'm not going to spend the time to do the coding necessary to make this
> all work properly in the first place...cause you know most users are
> willing to spend the minute to change the 2 or 3 symlinks, log out and back
> in..they'll want it to just work and then complain when one version of KDE
> hoses their config files for the other version and nothing works..then
> bitch even louder when they have to wipe their ~/.kde directory.
>
I don't think symlinking is the correct solution. There ought to be support
in build and runtime configuration for such an operation which seems to be
present ATM.
What I'd like to see is 3.x devel. packages working with 2.x
> If you want this ability then:
>
> 1: Figure it all out
> 2: Make sure it follows FHS
> 3: Make sure if follows Debian policy
> 4: Make sure it's very easy for a user to use
> 5: Submit a patch
I'll see what I can do for 3.x devel packages.
For now, it seems possible to use pkg*/dir instead of */dir
ie
/usr/share/<dir> --> /usr/share/kde3/<dir>
/usr/bin/<dir> --> /usr/bin/kde3/<dir> (why not? maybe some might get linked
to /usr/bin)
Or using /usr/lib/kde3 as the prefix to kde installation.
IMHO, the current directory layout is an obvious source of the problem.
I'll find exactly what prevents me from installing those harmless packages,
and then I'll post my findings here and then let's do the necessary changes.
I have in my mind something like an extra configuration where one may specify
which kde installations to use., ie what to set KDEDIRS to. We can do a GUI
for it if needed. (Or this might be unnecessary)
On #kde it's being recommended to compile&install stuff into a location such
as ~/kde3, but why not do it in the packages when we can? And in my opinion
if somebody wants to write a nice new app. or plugin, he ought to have easy
access to the next development environment of KDE.
In other words,
1. I agree that trying to support multiple versions of _application software_
may not be a brilliant idea. Though, that might even be possible. If they
don't work well, they shouldn't be made available.
2. Developers are debian users, too. In the case of debian even more so!
That's why I suggest we give them proper support and really have a
kde-cvs-dev working for the bees in the nest.
Regards,
- --
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE75gGafAeuFodNU5wRAobOAKCYbDCMl7J9t7U+Vc9ewSkOmNCSvgCgl7Kz
WTyYsWbzs5lZJIM0a/Wu8Lo=
=cLQ3
-----END PGP SIGNATURE-----
Reply to: