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

List:       kde-devel
Subject:    Re: [Bug 111915] no crystalsvg key_enter.png available in 32x32
From:       James Richard Tyrer <tyrerj () acm ! org>
Date:       2008-05-16 10:43:57
Message-ID: 482D656D.2070600 () acm ! org
[Download RAW message or body]

Kevin Kofler wrote:
> On Thursday 08 May 2008, James Richard Tyrer wrote:
>> Why don't you just use the current package that you have?
> 
> Because it's built from the kdeartwork-4.0 SRPM, once we upgrade to a version 
> of kdeartwork which has the new names, there goes the package. But changing 
> things around to build an equivalent package from the kdelibs3 SRPM instead 
> (or even a separate SRPM from the kdeartwork-4.0 tarball) is definitely 
> possible (and in fact what I mean by "reverting to the KDE 3 version"). But 
> at that point it's really a packaging issue.

Yes, you might have to make another SRPM, but building a package that 
doesn't contain any code is going to be rather trivial.

> The real issue will be making the version with KDE 4 names (once it exists) 
> coexist with the one with the KDE 3 names.
> 
The same issue exists with the Oxygen theme.  Actually, since Oxygen is 
the default with KDE4, it is more important to resolve the issue for the 
Oxygen theme.  The CrystalSVG icons are being used only because 
KIconLoader can't find the old names in Oxygen.

Take a look in $KDEHOME/.kde/share/config/kdeglobals

I think you will find:

	[Icons]
	Theme=oxygen

CrystalSVG is used only due to a kludge in the KDE3 library code.

-- 
JRT
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]