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

List:       kde-commits
Subject:    Re: Four solutions (Re: kdenetwork/kit/icons)
From:       Rob Kaper <cap () capsi ! com>
Date:       2002-10-31 23:52:58
[Download RAW message or body]

On Fri, Nov 01, 2002 at 12:26:45AM +0100, Martijn Klingens wrote:
> Can't you just release those icons in your tarballs? You need to package an 
> admin dir too. cvs2pack could even rename the cr-icons to hi-icons using a 
> flag if you prefer.

I can't release them in my tarballs as that would conflict with kdeartwork
3.1, as stated earlier. For some reason (say CERT finds spooky stuff) I
might want a seperate release during and for KDE 3.1.x as well.

> That would blow up the tarball sizes to unacceptable heights, so that's not an 
> option either.

It's not crud to have two icon themes in the main packages..

> > - upgrading a package requires not only a kdelibs upgrade, but also a
> >   kdeartwork upgrade. This should clearly documented and in the
> >   announcements. A new kdeartwork 3.0 is released with the hi* icons which
> >   have been removed outside of kdelibs which allows applications with
> >   third-party releases to be used with 3.0.
> 
> That's impossible to get right since the hicolor inheritance requires a 
> kiconloader update, so for KDE 3.0 user this is out of the question.

But for KDE 3.0 you won't need the inheritance since the hi* icons are
available from kdeartwork 3.0.x. That way the to-be-released apps will have
to require kdeartwork 3.0.x, but won't be force to require 3.1.

> If you want to release separately for 3.0 too (KDevelop, Kopete, Atlantik and 
> KOffice spring to mind here) you can either branch in CVS, add the icons 
> manually in the release tarball or add the required renaming/copying to 
> cvs2pack.

Well, fortunately someone made clear that hi* can continue to exist for
applications which don't have new cr* icons. Of course we'll run into the
same issues again when those icons will start to exist.

Hm, I could just add a dependency on kdeartwork>=3.1 for Atlantik in that
case, if kdeartwork-3.1 works fine with KDE 3.0. Branching in CVS to keep
3.0 compatibility for just a few icons.. well, if that's the best solution,
I'll consider it once someone actually makes cr* icons for Atlantik.

Rob
-- 
Rob Kaper     | Gimme some love, gimme some skin,
cap@capsi.com | if we ain't got that then we ain't got much
www.capsi.com | and we ain't got nothing, nothing! -- "Nothing" by A
[prev in list] [next in list] [prev in thread] [next in thread]