A new attempt on PyKDE5 binding generation

[Shaheed Haque]

I'm fine with this. The non-KF5 project (okular, marble, whatever)
would in any case have a dependency on KF5/Tier1 and so the fact that
the tooling lives there is probably fine. (And this essentially means
no change from how I am currently working, plus-or-minus a change of
repo name at some point).

Thanks for all the input/discussion.

On 7 April 2016 at 06:29, Scott Kitterman <kde at kitterman.com> wrote:
> On Thursday, April 07, 2016 12:16:58 AM Albert Astals Cid wrote:
>> So my suggestion would be renaming pykde5.git to pykf5.git, and that means
>> *only* KDE Frameworks 5 bindings would go in there, any other repo that
>> wants  to provide python bindings (say okular, marble or krita) should do
>> somewhere else, ideally their own repo so the binding and the original code
>> are close together and it's easier to keep in sync when api changes.
>>
>> Am I making sense?
>
> FWIW, I think this is exactly right.
>
> Scott K
> _______________________________________________
> Kde-bindings mailing list
> Kde-bindings at kde.org
> https://mail.kde.org/mailman/listinfo/kde-bindings
_______________________________________________
Kde-bindings mailing list
Kde-bindings at kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings