Il giorno Thu, 07 Apr 2016 00:16:58 +0200
Albert Astals Cid ha scritto:
> But personally I would not suggest having a "kde-wide" pykde5 repo
> given how many different release schedules we have now it would be
> close to unmanageable having a single repo that has kf5+marble+krita
> python binding
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
> some
El dilluns, 4 d’abril de 2016, a les 18:36:16 CEST, Shaheed Haque va escriure:
> Those build dependency and packaging questions are exactly why I keep
> making remarks about needing CMake help from folks who are familiar
> with current KDE build setups (and, maybe, packaging).
>
> So, to provide s
super cool!
replacing the current PyKF5 repo (and naming it PyKF5 surely is a
possibility?
Shaheed Haque schrieb am So., 3. Apr. 2016 um
14:32 Uhr:
> On 1 April 2016 at 23:18, Albert Astals Cid wrote:
> > El dijous, 31 de març de 2016, a les 23:04:07 CEST, Shaheed Haque va
> escriure:
> >> Tha
