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

List:       kde-bugs-dist
Subject:    [Bug 111915] no crystalsvg key_enter.png available in 32x32
From:       Kevin Kofler <kevin.kofler () chello ! at>
Date:       2008-05-07 22:01:01
Message-ID: 20080507220101.25320.qmail () ktown ! kde ! org
[Download RAW message or body]

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




------- Additional Comments From kevin.kofler chello at  2008-05-08 00:01 -------
> Yes, you would might need to use --replacefiles to install some KDE4 packages.

Once again: official Fedora packages CANNOT require --replacefiles (and I'm sure \
we're not the only distro which doesn't allow packages to replace each other's \
files)!

> But how do you leave KDE 3 libraries installed?

We have a kdelibs3 package which doesn't conflict with the KDE 4 version. We had to \
work hard on making it work. I don't see why we should do similar workarounds for \
crystalsvg when it's easy to support both sets of apps from the same sources.

> You need to install icons from KDE3 first and then install KDEArtWork from
> KDE 4.  There should be no problem with overwriting files.

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.

In addition, this means we have 2 copies of all the renamed icons when it would be \
much more space-efficient to have one copy and one symlink.

> But you will be running the KDE 3 app in KDE 4 and Oxygen will then be the
> default theme.

Not really.
* If the theme is not set in kdeglobals, KDE 3 apps will still default to crystalsvg.
* Even if you explicitly set your theme to Oxygen (or any other theme), the KDE 3 \
apps have a hardcoded fallback to crystalsvg and will use that if they can't find \
their icons in Oxygen (or whatever theme you picked). If (and only if) the icon isn't \
                in crystalsvg either, the app ends up with a broken icon.
* It's also possible for a distro's default icon theme to explictly inherit from both \
Oxygen and crystalsvg, which is what our Fedora-KDE theme does.

> One thing for sure, KDEArtWork for KDE 4 isn't going to include support for the old \
> names

And why? I really don't see a valid reason not to provide compatibility symlinks. For \
Oxygen, there was a reason (force apps to get ported to the new names), but for \
crystalsvg, supporting old apps should be on the contrary a requirement.


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