Bug 136186 - Separate Krita from KOffice to make it a standalone application
Summary: Separate Krita from KOffice to make it a standalone application
Status: RESOLVED INTENTIONAL
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR wishlist
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-23 16:01 UTC by Charles A. Landemaine
Modified: 2006-10-24 15:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles A. Landemaine 2006-10-23 16:01:14 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    FreeBSD Ports
OS:                FreeBSD

I would like Krita to be a standalone application so that if I want an office suite, I don't have to install an image editor, and if I want an image editor, I'm not forced to install an office suite.

MS Office doesn't ship with MS Paint, and MS Paint doesn't ship with MS Office.
Thanks in advance.
Comment 1 Inge Wallin 2006-10-23 16:09:19 UTC
If your packager has created the package of Krita as stand-alone, you will be able to install Krita standalone, otherwise not.  

This is a packaging bug and not a Krita bug; I suggest that you bring this bug to FreeBSD instead.
Comment 2 Cyrille Berger 2006-10-23 16:10:45 UTC
krita is allready an independant application. You don't need other application of koffice to run it or to compile it. If your distribution/os only offer a KOffice package, please report to them that they need to split it. Most linux distribution I know of (debian, ubuntu, fedora, mandriva, suse) have splitted package, I see no reason why it can't be the case for freebsd.

The reason why Krita is a KOffice application is because it use a lot of functions from KoLibs, using them has allow us to concentrate our efforts on essential feature of Krita instead of wasting our time reinventing what is in KoLibs
Comment 3 Charles A. Landemaine 2006-10-23 16:48:35 UTC
I see. I'll get in touch with the FreeBSD packager then. Thank you guys.
Comment 4 Charles A. Landemaine 2006-10-24 14:38:06 UTC
Here's a reply from Michael Nottebrock (lofi_AT_freebsd.org):

"You're not the first person to request this or something similar, but
unfortunately koffice is too integrated for its own good, especially at
buildtime - the applications cannot be separately built without
compiling a considerate part of the rest of the office suite each time,
which would be less of a problem if FreeBSD were as
binary-package-centric as most Linux distributions, but since most users
actually do compile KOffice from ports, and making each component of
KOffice a separate port would increase the build time for the whole
thing by close to 50%, it's not going to happen.

The next best thing you can do - use a binary package instead of
compiling the whole thing. Unless you're on a dial-up connection, this
should be considerably less time- and energy-consuming than building
from ports".
Comment 5 Cyrille Berger 2006-10-24 15:13:30 UTC
I am really sorry, but it is definitively a problem on the freebsd package system.
The last applications which needs to be build together are kword, kspread and kchart. All other applications can be seperated.

Plus, freebsd can make use of the variable DO_NOT_COMPILE, that allow to select components that you don't want to build. For instance, if the user of freebsd, only wants krita, setting DO_NOT_COMPILE="kword kspread kchart kpresenter karbon kformula kexi kplato kivio". There are a lot of solutions available to freebsd port writers.

And, please don't reopen this bug, the answer will allways be WONTFIX or INVALID.
Comment 6 Cyrille Berger 2006-10-24 15:15:18 UTC
Ah I forgot to mention that our FAQ explain a little bit more (and better than me) why krita is part of koffice http://www.koffice.org/krita/faq.php#WhyisKritapartofKOffice
Comment 7 Charles A. Landemaine 2006-10-24 15:17:59 UTC
Thank you Cyrille, the DO_NOT_COMPILE seems a good solution.