Bug 230056
Summary: | Latest fedora-logos requires 20 new unnecessary packages | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jarkko <jval> |
Component: | fedora-logos | Assignee: | David Zeuthen <davidz> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dgunchev, mclasen, smagoun |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-06-17 06:27:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jarkko
2007-02-26 11:50:51 UTC
Pendantic directory ownership rules require these dependencies. You should distribute the logos more targeted. There is an easy solution to this problem: Create subpackages in the spec files; one subpackage for each package (or package group) which uses the logos. Then make the depending packages to require the subpackage instead of the whole fedora-logos or redhat-artwork. At least redhat-artwork should be split I guess because that brings e.g. gtk2 to the list. I have a really easy (and also good, I think) solution to this problem. I bet all the other logos are related to a graphical environment (they are logos after all), except: /boot/grub/splash.xpm.gz I think with graphical environment those new dependencies are acceptable because you would have those packages installed anyway (e.g. you will end up with gtk2 anyway because Fedora tools use that). Just distribute that one (/boot/grub/splash.xpm.gz) separated, and at least my system would be fine with those new dependencies - because then I can remove fedora-logos as an unnecessary package (this is not a graphical system). Solution: Create a subpackage called fedora-logos-grub which provides grub-splash. Then change grub to require grub-splash instead of system-logos. having all trademarked fedora logos in a single package is a requirement from RH legal. In a single binary package? Or just source? My suggestion still keeps everything in one source package. I don't like the situation too: - Why a minimal non-GUI system (i.e. simple router/firewall) should have fedora-logos (and GTK and...) installed for of grub? Grub works just fine without any logo (but 'rpm -e --nodeps --force fedora-logos' is much more wrong). - Why a KDE only desktop (just hypothetically, I always have KDE, GNOME, XFCE4... installed) have GTK and so on installed? If/when system-config-* get ported to KDE... Does one source package solve the legal problem (I hope so, good idea Jarkko)? * Fri Jun 15 2007 Adam Jackson <ajax> 6.0.98-4 - Remove the Requires on redhat-artwork and fedora-icon-theme, and just multi-own the directories. Fixes some hilarious dependency chains. |