calligra 3.0.0 tarball

[Dag]

Boudewijn Rempt skrev den 2016-12-08 11:53:
> On Thu, 8 Dec 2016, Dag wrote:
> 
>> 
>> 
>> Boudewijn Rempt skrev den 2016-12-08 11:13:
>> > On Thu, 8 Dec 2016, Dag wrote:
>> >
>> > > Hmmm, well does this mean krita translations will be released/packaged
>> > > with
>> > > calligra release? If so, there is bound to be problems sooner or later. Or
>> > > is/can this be taken care of in some way?
>> >
>> > I guess I can add some code, if I remember a bit of ruby (it's years since
>> > I last used it) to skip everything that sounds like krita or kexi.
>> Yes well, when calligra is released, when krita is released skip
>> calligra/kexi, and when kexi is released...
>> Maybe the best solution, but doesn't sound great.
>> 
> 
> Well, for Krita, we only have krita.po with everything in it -- so that 
> works
> out automatically. I'm not sure about kexi, though.
Ehhh, no not quite, there is also desktop_calligra_krita.po and 
org.kde.krita.appdata.po, but still...
My concern is the future when something is added/changed.

I can't see more than two possible sustainable solutions:
Best: split calligra, kexi and krita properly both in git and svn.

Not so good: Make some cmake magic to install only the po files we can 
generate pot files for. This will work for all of us, except that there 
will be another special solution to maintain. But it will not solve the 
"problem" that it is less straight forward for the translators as always 
only parts of "calligra" (as they see it) is released.