On Mon, 30 May 2016, Jaroslaw Staniek wrote:


Hi Boud,
Is the situation different in this regard than it was in KOffice 1 -> Calligra 
2 time?
Co-installation was not there and is not here in case of Calligra 2/3 apps. 
Maybe package(s) of Krita 3 can be marked as obsoleting calligra-krita (2),
whatever the package name is in given distro.

_If_ distributions can do that without obsoleting also calligralibs -- I'm not 
sure about that.


Perhaps we can afford to have proper update for README.PACKAGERS.

Somewhat apparent change is lack of krita -> calligralibs dependency but it's 
kind of transparent for users.


On 30 May 2016 at 16:39,
​​Friedrich W. H. Kossebau <kosse...@kde.org> wrote:
      Hi,

      Am Montag, 30. Mai 2016, 16:14:32 CEST schrieb Boudewijn Rempt:
      > Hi,
      >
      > Tomorrow we'll release Krita 3.0.

      So awesome to have reached that point :)

      > At that point, the stable version
      > of Krita is no longer part of Calligra. On the other hand, Krita is
      > still part of the last stable release of Calligra, which makes it
      > hard for distributions to package both and make them coinstallable.

      Does it? Did anyone report problems?

      > When we split up Krita and Calligra I had expected both projects to
      > release more or less at the same moment, especially because the port
      > seemed to have posed much fewer problems for Calligra than for Krita.
      >
      > The question is: what do we do now? I guess there are three options:
      >
      > * Also release Calligra 3.0 Really Soon Now

      Sadly not possible, given the lack of dev resources at the moment.

      > * Make a Calligra 2.9 release without Krita

      Would that be really needed? Unless some distri packages all of Calligra 
into
      one package (which would be aweful and IMHO not supported by us), 
packagers
      should be able to create packages of new Krita next to packages from the 
old
      calligra, no?

      > * Accept the problem and do nothing

      Packagers could be told to use the cmake flag "-DBUILD_krita=off" with the
      existing calligra 2.9 tarball, that should in theory work to skip krita. 
But
      well, I am not sure what the problem is.

      > There is a simular problem with the calligra.org website: when will
      > we remove Krita from the website? When there's a new Calligta
      > release, now that there's a new Krita release, or...

      IMHO as soon as Krita 3 is out. The old landing page on calligra.org/krita
      would tell about Krita now grown up to be a project of its own.


@Cyrille: Would you be able to update the site with at putting least proper 
links to krita.org? Or hand over to someone else.

A short list:
- ​I have no access here:
​update the menu by removing Krita​ (2 places)
-Editing possible, I can try: remove the 
https://www.calligra.org/tour/calligra-suite/graphics-applications/​ and unlink 
it from
https://www.calligra.org/tour/calligra-suite/
-Editing possible, Boud: would you try? calligra.org/krita page stays (as it's 
target from elsewhere in the internet) but needs update - mentioning the
change
-calligra.org artwork - I am volunteering to cut off one app :)
-places such as wikipedia would need updates, please consider changed for your 
language :)
​ 
      _______________________________________________
      calligra-devel mailing list
      calligra-devel@kde.org
      https://mail.kde.org/mailman/listinfo/calligra-devel




--
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek



--
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel

Reply via email to