[prev in list] [next in list] [prev in thread] [next in thread] 

List:       calligra-devel
Subject:    Re: After 2.9.7
From:       Dmitry Kazakov <dimula73 () gmail ! com>
Date:       2015-08-31 9:50:12
Message-ID: CAEkBSfVkZBcJTcm+rSEM16iE4dp4Eq7vPaa8dF=ZHquoEucpKg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


> 1) I'm ok with forking Krita repository. We already depend from quite few
>> libraries from calligra libs. That is mostly, KoCanvasBase, KoDocumentBase,
>> flake and pigment.From all four only pigment looks
>> reusable enough for me to have a separate repo. In our code we hack quite
>> a lot to adapt flake and document classes for our needs.
>>
>> 2) One more benefit of forking to another repository would be that the
>> size of the repo would become lower (correct me if I'm wrong). Since "Krita
>> for Cats" manual is still semi-official way of building
>> Krita on some platforms this is really crucial for many users. Quite a
>> lot of people still have GPRS or limited internet, so downloading 700MiB
>> just to try Krita *is* a barrier. Another problem is
>> translators. Basically, they need to have a full source tree around to be
>> able to check where the string comes from.
>>
>
> The repo size is one reason I'm actually considering to drop all
> history. Create a fresh new repo with cleaned-up code only and start
> again from commit 0. I know we check history a lot, but that history is
> the history of Krita up to Krita 2.9.x, which is in the calligra repo.
>

This will make our life really hard :(
  <calligra-devel@kde.org>
-- 
Dmitry Kazakov

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class=""><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> 1) I&#39;m ok \
with forking Krita repository. We already depend from quite few libraries from \
calligra libs. That is mostly, KoCanvasBase, KoDocumentBase, flake and pigment.From \
all four only pigment looks<br> reusable enough for me to have a separate repo. In \
our code we hack quite a lot to adapt flake and document classes for our needs.<br> \
<br> 2) One more benefit of forking to another repository would be that the size of \
the repo would become lower (correct me if I&#39;m wrong). Since &quot;Krita for \
Cats&quot; manual is still semi-official way of building<br> Krita on some platforms \
this is really crucial for many users. Quite a lot of people still have GPRS or \
limited internet, so downloading 700MiB just to try Krita *is* a barrier. Another \
problem is<br> translators. Basically, they need to have a full source tree around to \
be able to check where the string comes from.<br> </blockquote>
<br></span>
The repo size is one reason I&#39;m actually considering to drop all<br>
history. Create a fresh new repo with cleaned-up code only and start<br>
again from commit 0. I know we check history a lot, but that history is<br>
the history of Krita up to Krita 2.9.x, which is in the calligra repo.<span \
class=""><br></span></blockquote><div><br></div><div>This will make our life really \
hard :(<br></div><div class="h5">  <a href="mailto:calligra-devel@kde.org" \
target="_blank"></a><br></div></div>-- <br><div class="gmail_signature">Dmitry \
Kazakov</div> </div></div>


[Attachment #6 (text/plain)]

_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel


[prev in list] [next in list] [prev in thread] [next in thread]