[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-07 23:33:20
Message-ID: 48223C40.4020301 () acm ! org
[Download RAW message or body]

Excuse me for CCing two lists but I really don't know if this is an
Artist issue or not.

Rex Dieter wrote:
> ------- You are receiving this mail because: ------- You are on the
> CC list for the bug, or are watching someone who is.
> 
> http://bugs.kde.org/show_bug.cgi?id=111915 rdieter math unl edu
> changed:
> 
> What    |Removed                     |Added 
> ----------------------------------------------------------------------------
>  CC|                            |rdieter math unl edu
> 

Rex:

I would value your input on this, but please lets discuss it on a
mailing list since it has nothing to do with this bug.

If you don't think that the KDE-Devel list is appropriate, then suggest
one that you would prefer.

IIUC, taking comment #14, that there is a package:

	 kdelibs3-3.5.9-8.fc9.i386.rpm

which can be installed along with a KDE-4 installation.

The KDE-4 installation will include:

	kdeartwork-4.0.3-3.fc9.i386.rpm

Now, I am left with a great mystery since neither of these packages 
contains the icons.  Where are the CrystalSVG icons?  If the RPMs 
correspond to the KDE SVN modules then the icons should be in both of 
them, but it is in neither.  The icons are actually in:

	crystalsvg-icon-theme-4.0.3-3.fc9.i386.rpm

Kevin Kofler said in Bugzilla.

> This doesn't work when packaging. When packaging, we do one RPM from
> the kdelibs 3 sources and one from the kdeartwork 4 sources, and the
> RPMs are not allowed to have conflicting files.

This is obviously not true.  What is true is that when that happens and 
an update is performed that the files from the newer RPM overwrite the 
files from the older rpm.  There is no problem with the old and new icon 
names because the new name will not overwrite the old name.

Since the icons are not in more than one package, there is no problem 
with overwriting any files.

The package: crystalsvg-icon-theme-4.0.3-3.fc9.i386.rpm should have the 
new XDG standard icon names in it.

Yes, there is an issue with KDE-3 applications needing icons with the 
old names.

However, I still think that since this is not an issue if you build from 
source that this is just a packaging issue.  Fedora should provide a 
package that contains either the icons with the old (KDE-3) names 
(should be Oxygen icons) or symbolic links for the old names.

If KDE needs to support this, we need to provide a script and data to 
make the symbolic links in whatever icon theme the script is pointed at. 
  It is not a question of CrystalSVG being the default for KDE-3 since 
if you install KDE-4 then the default theme is Oxygen and the KDE-3 apps 
are finding the CrystalSVG icons because they have the old names.

-- 
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]