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

List:       kde-core-devel
Subject:    Re: RFC: Creation of a new KDE SC module [kdeplugins]
From:       todd rme <toddrme2178 () gmail ! com>
Date:       2010-10-11 23:41:43
Message-ID: AANLkTiniVtfzzP4CiRT5phdbKAAeLzR-dJyQkEFu6PPM () mail ! gmail ! com
[Download RAW message or body]

On Mon, Oct 11, 2010 at 7:00 PM, Sune Vuorela <nospam@vuorela.dk> wrote:
> On 2010-10-11, Martin Gräßlin <kde@martin-graesslin.com> wrote:
>>> No. you also cannot guarantee that they are in sync with kwin if they
>>> are not build from the same tarball as kwin.
>> I thought there was versioning possible with CMake? So we can ensure that e>>.g. 
>> the effects with 4.6.2 are only built against kwin from 4.6.2. We can even >> add 
>> a packager file, to explain how the requirements should be set. Of course i>> f 
>> someone wants to screw up he will always be possible to do so.
>
> Joe User goes to kde.org and downloads and builds kdelibs, kdepimlibs,
> kdebase-runtime, kdebase-workspace and the nonexistant kdeplugins  all
> version 4.6.0. Now he does nothing for 6 months, and downloads and
> builds kdelibs, kdepimlibs, kdebase-runtime and kdebase-workspace, but
> *not* kdeplugins.
>
> Jane Packager downloads and packages 4.6.1 for her distro, for 4.6.2 she
> notices that the only diff between 4.6.1 and 4.6.2 in the kdeplugins
> module is the change of version number and chooses to spend her time on
> more important issues.
>
> I don't consider these cases 'screwing up', but very likely situations.
>
> /Sune


How is this different than any other non-core part of KDE SC?  For
instance, kdeutils, or kdeedu?

-Todd

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