No KDE 3.3 from Mandrake?

Alex Nordstrom alexander.nordstromDONT_CC_ME at
Mon Sep 6 04:18:53 BST 2004

On Monday, 6 Sep 2004 09:27, Zé wrote:
> Em Segunda, 6 de Setembro de 2004 02:07, o Alex Nordstrom escreveu:
> > On Monday, 6 Sep 2004 07:16, Zé wrote:
> > > There arent packages og kde3.3 for mandrake, in cooker there
> > > still are kde3.2.3.
> > > so what i suggest (that is what i do), is to have the kde
> > > installed of mandrake, and then to have the latest kde and still
> > > have the menus in menudrake, is to download the sources from
> > > and compile them that they will overwrite the kde
> > > binarys installed.
> >
> > Overwrite the binaries provided by the package management system of
> > your distribution with locally compiled files? That's what
> > /usr/local is for. I'm beginning to suspect what the origin of some
> > of the bizarre KDE and KMail problems you seem to be having might
> > be.
> Well ur completly wrong, cause i just installed now kmail-1.7, still
> yesterday i was using kmail-1.6.2.

Installing locally compiled files in /usr/bin is a bad idea irrespective 
of version numbers.

> Now the only diference is that im using kmail-1.7 compiled from
> sources. cause Mandrake doesnt have it.

You mentioned using a self-compiled version before as well. And if 
you've been doing it that way with KMail or other KDE components whilst 
still using your distribution's package management system, trouble is 
to be expected.

What do you think happens if you have $PROGRAM 1.0-1 installed by the 
package management system, overwrite (parts of) it with version 1.1 
from source (which possibly adds other files as well), and then accept 
an "upgrade" to 1.0-2 from the package management system (which isn't 
aware that you have 1.1 installed)? You'd very likely have old 
components trying to work with new components and vice versa in very, 
very strange ways. It really is asking for trouble.

-- it's there for a reason.

> And by the way, it overwrites the kdepim binarys cause by default
> intalls them in /usr/bin, theres no need to specify
> --prefix=/usr/local because this configure by default installs them in
> the kde dir that is known by doing the  command kde-config --prefix

From the INSTALL file in the kdebase source archive:
> By default, `make install' will install the package's files in
> `/usr/local/kde/bin', `/usr/local/kde/lib', etc.  You can specify an
> installation prefix other than `/usr/local/kde' by giving `configure'
> the option `--prefix=PATH'.

On Monday, 6 Sep 2004 09:27, Zé wrote:
> Tipicall of you being guessing...

Couldn't resist, could you? Well, better to raise questions than to rush 
on like a brainless buffalo. Are you normally this hostile when people 
offer to help you?

Alex Nordstrom
Please do not CC me in followups; I am subscribed to the kde list.
This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list