KDE Addons Package Standards
Purpose
To develop a standard package naming scheme for add-on packages (such as themes) of other applications/system elements in the Fedora-KDE universe.
Naming scheme
- Clipart need not be DE specific and should be named
clipart-%{packagename}
- KDE color schemes should be named
kde-colors-%{packagename}
- KDE Cursor packs should be named
kde-cursors-%{packagename}
- KDE window decorations tend to come in several forms/types: Comiz, IceWM, deKorator, and native. They should be named
kde-decoration-%{type}-%{packagename}
- Kopete emotion packs should be named
kde-emoticons-%{packagename}
- KDE icon packs should be named
kde-icons-%{packagename}
- Karamba applets should be named
kde-karamba-%{packagename}
- Items that do not otherwise fit into other categories should be named
kde-misc-%{packagename}
- KDE screen savers should be named
kde-screensaver[s] -%{packagename}
- Service menus for KDE should be named
kde-servicemenu[s] -%{packagename}
- KDE Splash Screens should be named
kde-splash[s] -%{packagename}
- KDE widget styles should be named
kde-style-%{packagename}
- General themes for KDE should be named
kde-theme-%{packagename}
- Themes for Amarok should be named
kde-theme-amarok-%{packagename}
- Themes for k3b should be named
kde-theme-k3b-%{packagename}
- Themes for KBFX should be named
kde-theme-kbfx-%{packagename}
- Themes for KDM should be named
kde-theme-kdm-%{packagename}
- Themes for Noatun should be named
kde-theme-noatun-%{packagename}
- System event sounds should be given a non DE specific name
sounds-%{packagename}
- Bitmap wallpapers should be given a non DE specific name and should also contain information about the dimensions with the values being zero padded to 4 digits in the format of
wallpaper[s] -%{width}%{height}-%{packagename}
- SVG wallpapers should be given a non DE specific name
wallpaper[s] -svg-%{packagename}
- [s] represents optional, but descriptive pluralization: ie. wallpaper-svg-foo-1.0-1.noarch.rpm will contain one wallpaper (file) while wallpapers-svg-foofoo-1.0-1.noarch.rpm will contain two or more files
Complaints
Complaint: A lot of Gnome users use Amarok, so kde-themes-amarok-%{packagename} should be replaced by amarok-theme-%{packagename}
Response: Amarok is still arguably a KDE centric application built with Qt and KDE bindings. The solution may be to come to a definition on what constitutes a KDE app. However, taken to the extreme, this would lead to amarok being renamed to kde-amarok, the affect of this change being uncertain. While such a change would make yum list "kde-*" more useful, it would be a large change to track down all such programs and may lead to unnecessary segregation of packages.
Complaint:
It may be nicer to have kde-splash instead of kde-splashscreens.
String length really should not be an issue. But the omissions of 'screens' doesn't seem to take away to much from its descriptiveness.
Problems
Problem: Current Purpose may be too broad.
Suggestion: Change Purpose to the following: To develop a standard package naming scheme for add-on packages (such as themes) of other applications/system elements in the Fedora-KDE universe.
Problem: Differentiate between KDE3 and KDE4 packages
Suggestion: s/kde/kde3/ or s/kde/kde4/ depending on what they target
Problem: need to distinguish between themes only using Qt and those actually using KDE
Suggestion: (none yet)
Arising Proposals
Define a KDE application as a application as one that meets some or all of the following requirements:
- is specifically built to solve a KDE problem/need
- is a GUI application built with the Qt toolkit and contains the recognizable 'K' in its name
- is a GUI application built with Qt and KDE bindings/libraries
Contributors
- Arthur Pemberton <pembo13 at gmail dot com>
- Rex Dieter <rdieter at math dot unl dot edu>
- Chitlesh Goorah <chitlesh at fedoraproject dot org>
- Francois Aucamp <faucamp at csir dot co dot za>