KPeople part of KDE Frameworks

[Marko Käning]

Hi Michael,

On 03 Mar 2015, at 03:30 , Michael Pyne <mpyne at kde.org> wrote:

> On Mon, March 2, 2015 20:15:20 Marko Käning wrote:
>> So, having those ktp-* entries in dependency-data-stable-kf5-qt5 shouldn’t
>> do any harm.
>> 
>>   But I don’t know how kdesrc-build will handle this, though...
> 
> For missing entries kdesrc-build will infer "master" as the git branch to use. 
> It would be very confusing for a user to ask to build a module and still have 
> kdesrc-build ignore it because it doesn't have an entry in kde-build-metadata.
> 
> With that said, kdesrc-build *will* ignore modules that have a defined branch 
> of "" (i.e. empty) in logical-module-structure, so if a module simply should 
> not be built for a given branch-group my recommendation would be to define the 
> branch-group after all but set it to an empty value. E.g.
> 
>        "kde/kdenetwork/ktp*": {
>            "stable-qt4": "kde-telepathy-0.9",
>            "latest-qt4": "kde-telepathy-0.9",
>            "kf5-qt5": "master",
>            "stable-kf5-qt5": ""
>        },
> 
> I believe that Scarlett's new CI supports this as well, and the current 
> Jenkins CI also supports this.

Scarlett’s CI also supports to treat *undefined* entries as _set to empty_,
just like my OSX/CI does.

   So, in the light of your remarks the question is, whether all the
   removed empty definitions in my RR [1] should actually be left the
   way they are!?!?

Greets,
Marko


[1] https://git.reviewboard.kde.org/r/122672/