Kdev-clang master not building
aleixpol at kde.org
Mon Apr 27 13:06:58 UTC 2015
Replying Andreas comment, which was sent only to me.
On Mon, Apr 27, 2015 at 2:54 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> On Mon, Apr 27, 2015 at 1:13 PM, Aleix Pol <aleixpol at kde.org> wrote:
>> I just asked Jonathan, he said that they expect to be able to update
>> releases from time to time, if there aren't known regressions.
>> Of course that's not a reason for depending on master (although it's
>> quite convenient if we want developers to help fixing frameworks,
> Can one run multiple versions of KF5 on a single system when one of those
> versions is installed in /usr? After all the original issue here is that
> people now start to run Plasma 5 based desktops and hence will have kde
> frameworks installed in /usr. If an application needs newer frameworks then
> those need to be installed somewhere in $HOME or so and they must not
> interfere in any way with the system installed version. That still ignores
> the problem of having to manually build and update all those frameworks - in
> particular having to wait for the build to finish.
Yes, it works. RPATH should take care of this.
We also have to do the same for kdevplatform and kdevelop. git pull and install.
>> IOW, thanks for introducing the fallback for previous versions but
>> please let's not stick to a release number just because.
> KDevelop 4 master depended on kdelibs master in its early days of
> development, but most of us didn't run a KDE4 desktop session until 4.2 or
> so. So having the kde4 libs installed in your home and not interferring with
> the main desktop wasn't a big issue. That was convenient back then since we
> did contribute quite a bit into kdelibs at that time.
> Once released however KDevelop's master always required only released
> kdelibs versions AFAIK, except maybe for the occasional thing in
> Anyway, all I wanted to say is that having an app's (any application, not
> just kdevelop) master branch depend on core system libraries master version
> (and in a Plasma 5 session all framework libs are to be considered core
> system libraries as they're needed for the desktop session) is a major
> headache for occasional contributors that want to hack a little on that app.
I understand and agree. :)
More information about the KDevelop-devel