DevHeads.net

libkactivities moved to kactivities repository

hi...

the library in kdelibs/experimental/libkactivities has been moved to a
separate git repository: kactivities.

the reason for this is two fold:

1) this is what we want to do for Frameworks development anyways: multiple
repositories ...

2) currently Plasma Active requires kdelibs to be built with the active-
development/4.7 branch. i merged all changes except the changes to
libkactivities into KDE/4.7 (they were all bugfixes to libplasma, it turns
out). the library had simply changed too much to merge it into the KDE/4.7
branch. so .. into its own repository it goes. this will allow plasma-mobile
and the share-like-connect repositories to be built and be functional with
normal kdelibs (KDE/4.7 branch, e.g.) along with the kactivities repository

all developer of libkactivities should happen in this new repository. i will
be removing the active-development/* branches in kdelibs shortly.

Comments

Re: libkactivities moved to kactivities repository

By Marco Martin at 09/15/2011 - 09:52

On Wednesday 14 September 2011, Aaron J. Seigo wrote:
ther is still one important thing left in active-development/4.7 that *really*
would have to be ported to 4.7 if we want to use that branch: the changes to
packageStructure, otherwise no launcher, no activity switcher, no
recommendations overlay :/

Cheers,
Marco Martin

Re: libkactivities moved to kactivities repository

By Marco Martin at 09/15/2011 - 09:58

On Thursday 15 September 2011, Marco Martin wrote:
to be more precise, it's those 3:

11e2edc76dca224ec0377cbf2fc3c90eac279d39
820caecc083927e96b53e59467acb912e2922062
e53be6503d8ae4129e0df58b5e9679395918cbc9

Re: libkactivities moved to kactivities repository

By Marco Martin at 09/14/2011 - 11:34

On Wednesday 14 September 2011, Aaron J. Seigo wrote:
the same thing should be done in kde-runtime, i gave a quick look to the
defferences between active-development/4.7 , active-development/master and
master, the diffs are attached.

now seems that the difference between active-development/4.7 and KDE/4.7 is
much bigger than active-development/master and master, partly is obvious
because all undel plasma/ is already in master as well, at least i taken care
of that for my commits,

but there is also a bigger difference in the activitymanager.

now, are all patches related to the activitymanager that are in active-
development/4.7 in active-development/master as well?

Ivan: do you remember if all your changes in activitymanager are both in 4.7
and master branches of a-d?

Cheers,
Marco Martin

Re: libkactivities moved to kactivities repository

By Aaron J. Seigo at 09/16/2011 - 05:10

On Wednesday, September 14, 2011 18:34:21 Marco Martin wrote:
there are three sets of changes in there: activitymanager, nepomuk and plasma.

the nepomuk one first, since that's the smallest: it's a patch to
nepomuk/ontologies/kext.trig .. it's seems to be things for activitymanager.
can these be packaged with activitymanager itself? or must it be part of the
nepomuk runtime package? (i'm thinking of a possible resolution where nepomuk
runtime is install first, and then activitymanager is..)

activitmanager: this should simply be moved into the kactivities module. the
consensus from Platform 11 was that runtime components that are tightly
coupled to a given library should travel with it in the same repository. i'm
still only 80% convinced of this, but consensus overrules that ;) this
resolves that issue cleanly, though it will create the awkward situation for
using kactivities with kde-runtime 4.7 of a file in kde-runtime being
overwritten by one in kactivities ... still, it's what we ought to do for the
long term. we could perhaps, with packager approval, remove activitymanager
from kde-runtime/4.7 and require the use of the kactivities repo instead.

the plasma changes look like they should simply be merged over.

Re: libkactivities moved to kactivities repository

By Marco Martin at 09/14/2011 - 14:31

On Wednesday 14 September 2011, Marco Martin wrote:
update on kde-runtime:
now, what should have been the only commit in active-development/4.7 not in
master is there too.
that means that master and a-d/4.7 *should* be interchangeable without
problems.

we could say test and see.

i'm not 100% sure whether kde-runtime master is safe enough or not for PA1,
while there isn't much activity in most of it, there is a lot in nepomuk
runtime, that adds up a bit of uncertainy..

Cheers,
Marco Martin