KOffice Creativity Package name

Thomas Zander zander at kde.org
Thu Nov 1 19:05:48 CET 2007

On Thursday 01 November 2007 18:31:12 Cyrille Berger wrote:
> On Thursday 01 November 2007, Thomas Zander wrote:
> > On Thursday 01 November 2007 16:07:56 Cyrille Berger wrote:
> > > That would probably
> > > result in some changes in how tarball(s) are released
> >
> > I think its great if KOffice can be marketed directly to the artists
> > and allow them to ignore KWord if they just want to use an artistic
> > application.
> As I said the word "office" is repealing to most artists with who we
> have discussed this issue. 

And I agreed, hope that was clear :)

> > Very much like there is no need to release 10 tarballs because users
> > want to install Krita without having to install KWord.
> The way KOffice is packaged is very different in various distributions,
> ranging from a all-in-one package, to an everything is splitted
> (including plugins without correct dependencies, or even a very funny
> libkofficegrayau8colorspace5 in Mandriave 2008 :D ) to thematic
> grouping.
> So while I know that you believe that we should leave packaging to
> distributions, I believe we need to be proactive 

Ok, fair enough.
First question that I have here is what is *wrong* with how its done now, 
or, what could be done better.

There are some solutions you might want to try out; the first is talking 
to distros either directly, or by providing a readme.  I don't really 
care with medium is used, but a discussion can be opened with them.
If that fails (did we already try?) we can look for other ways to do this.

In the context of this mail, I think we can suggest them to make an extra 
meta-package which will install krita + karbon. But naturally not 

Just to be clear, such a solution will in no way effect the packaging of 
the current 'koffice' meta package.

> > So, again, I love the idea, if you guys can pull it off, thats
> > wonderful. At the same time it should not affect the current message
> > KOffice sends out. Just complement it.
> Or clarify it. Because, trully, I have yet to find someone outside the
> KOffice project that understand the "message". I don't know anybody who
> hasn't ever asked me "but why Krita is part of an Office Suite ?"

And marketing the artistic package separate is a great idea.  It means 
that people can see Krita as a separate thing and don't have to know 
there is something called KOffice.

Again, we most probably agree.

One thing I want to make very clear, though, is that this will not in any 
way mean Krita needs to step out of KOffice.  We had this discussion 
already with KOffice falling under the KDE umbrella, but that when people 
looking directly for KOffice we don't make any association with KDE 
because people might mistakingly think they *need* KDE.
Similar, people looking directly for Krita or Karbon will be able to find 
your new website etc.  No need to state it is part of KOffice as people 
can use Krita without knowing its part of KOffice (or KDE for that 

The creativity package thing is really showing we are maturing and some 
parts can stand on their own. I just want to make clear that adding the 
concept that some apps are creative will not have any effect on KOffice 
as a whole.

Or, for the more technically inclined people;  you can create a new svn 
repository 'creativity' which just svn-externs krita and karbon (etc).
The externing means that the code will still be visible from the 
koffice-repo as well.

Thomas Zander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kimageshop/attachments/20071101/b3ac9c05/attachment.pgp 

More information about the kimageshop mailing list