[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kconfig_compiler moved to libexec
From:       David Faure <faure () kde ! org>
Date:       2007-05-16 7:56:47
Message-ID: 200705160956.48001.faure () kde ! org
[Download RAW message or body]

On Tuesday 15 May 2007, Oswald Buddenhagen wrote:
> On Tue, May 15, 2007 at 12:44:15AM +0200, David Faure wrote:
> > Because kconfig_compiler moved from bin/ to lib/kde4/libexec,
> >
> now, that confuses me a bit - this is a development tool, but not really
> a runtime helper (which libexec is for - executables with lib
> character). am i missing something?

Hmm, you are correct. I was given a list of conflicts between kdelibs3 and kdelibs4,
(committed to kdelibs/CONFLICTS) but that list contains all the development tools,
which are not a problem since only the development tools for one of
the two kde versions can be installed at a given time in a given prefix
(due to the .so symlinks).

Now what... should I revert the kconfig_compiler move? 
Being in libexec doesn't really hurt either -- except for people trying to build their
own kde app with something else than cmake (good luck to them...)

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
[prev in list] [next in list] [prev in thread] [next in thread]