From kde-core-devel Fri Oct 12 18:31:48 2007 From: "Jason 'vanRijn' Kasper" Date: Fri, 12 Oct 2007 18:31:48 +0000 To: kde-core-devel Subject: Re: kdelibs 3/kdebase 4 co-installable ? Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=119221396225306 MIME-Version: 1 Content-Type: multipart/mixed; boundary="------=_Part_29202_27689056.1192213908400" ------=_Part_29202_27689056.1192213908400 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 8/13/07, Fathi Boudra wrote: > > hi, > > in the similar idea of the kdelibs 3/4 conflicts thread, > any plans to make kdelibs 3/kdebase 4 co-installable ? > > so far, we have kdelibs 3 and kdelibs/kdepimlibs 4 co-installable. > we have tested kdelibs/kdepimlibs/kdebase 4 with kdelibs 3 and conflicts: > > /usr/share/icons/crystalsvg/*/actions/knewstuff.png > /usr/bin/kcmshell > /usr/bin/kstartupconfig > /usr/bin/kioexec > /usr/bin/khotnewstuff > /usr/bin/kfile > /usr/bin/imagetops > /usr/bin/kinstalltheme > /usr/bin/kdostartupconfig > > cheers, > > Fathi > I didn't realize that this was a problem still, but pusling (fearless debian dude) was telling me that this problem still exists today. I know we went to some degree of effort in trying to pre-empt this with the likes of kbuildsycoca4, etc. Is there a strategy for getting past the kdelibs3/kdebase4 package conflicts, does anyone know? -- -[ Jason 'vanRijn' Kasper // http://movingparts.net ]- -[ KDE PIM Developer // http://www.kde.org ]- -[ bash fun -> :(){ :|:&};: // Numbers 6:22-26 ]- ------=_Part_29202_27689056.1192213908400 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 8/13/07, Fathi Boudra <fboudra@gmail.com> wrote:
hi,

in the similar idea of the kdelibs 3/4 conflicts thread,
any plans to make kdelibs 3/kdebase 4 co-installable ?

so far, we have kdelibs 3 and kdelibs/kdepimlibs 4 co-installable.
we have tested kdelibs/kdepimlibs/kdebase 4 with kdelibs 3 and conflicts:

/usr/share/icons/crystalsvg/*/actions/knewstuff.png
/usr/bin/kcmshell
/usr/bin/kstartupconfig
/usr/bin/kioexec
/usr/bin/khotnewstuff
/usr/bin/kfile
/usr/bin/imagetops
/usr/bin/kinstalltheme
/usr/bin/kdostartupconfig

cheers,

Fathi

I didn't realize that this was a problem still, but pusling (fearless debian dude) was telling me that this problem still exists today. 

I know we went to some degree of effort in trying to pre-empt this with the likes of kbuildsycoca4, etc.  Is there a strategy for getting past the kdelibs3/kdebase4 package conflicts, does anyone know?

--
-[ Jason 'vanRijn' Kasper    //  http://movingparts.net ]-
-[ KDE PIM Developer         //  http://www.kde.org  ]-
-[ bash fun -> :(){ :|:&};:  //  Numbers 6:22-26 ]- ------=_Part_29202_27689056.1192213908400--