Re: KDE 3.2-beta2
måndagen den 30 september 2002 02.30 skrev Ben Burton:
> Hmm, just out of interest, what's the specific reason for having two
> separate branches of KDE 3.1 packaging? I just took a look at the sources
> and there do seem to be some non-trivial splits between your versions and
> the CVS versions that the maintainers are updating.
>
> I'm not hassling you here, I'm just curious. :)
An old letter. I think I never answered.
The main reason for the things I have done is so you can install an
application with the current version of KDE, and it will work even when you
upgrade KDE. That's not possible with the current packaging method.
This is a constant problem with KDE on debian. All the old KDE apps break when
you upgrade KDE. The way I have made it, there is chance that an application
will work even when main KDE is upgraded to 3.2 and so on. This since the old
libraries can co-exist with the new ones.
The GCC3 upgrading will break every single old KDE app, won't it?
I think I am not to only one, that finds an app, try to install it, and finds
that apt tells me that it will remove kdelibs4 + a lot of other libraries,
and install kdelibs3 + a lot of other stuff. Now I know what that means, and
can abort the installation, but how about a normal user? If you don't abort
it, you can get into real deep trouble, with half of one KDE version
installed, and half of another. A situation that apt is sometimes not able to
get out of, and you have to fix it up with dpkg.
-- Karolina
Reply to: