system-splash.png and derivatives

[Alan Milligan <alan balclutha org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

One thing that really frustrates me about anaconda is that it's splash
screen generation sucks -at least for anaconda <= FC4 - I'm not enough
of a masochist to try the latest devel packages ;)

system-splash.png is located in fedora-logos (or redhat-logos).  When
creating a Linux derivative distribution, the first thing we do is
create a new -logos package (the second thing is a new -release package).

However, upd-instroot hard-codes redhat-logos and fedora-logos into it's
packages and thus does not unpack our -logos and then barfs when
system-splash.png is not found.

What I'd like to see instead, is something similar to the tzdate logic,
where it checks through the %{PROVIDES} to discover this (maybe look for
provides redhat-logos).

At the moment, we have to cut new anaconda packages for each derivative
- - with this change, we wouldn't need to.  Another less glamorous option
could be to pass this as a parameter to buildinstall, but I'd prefer to
use the knowledge contained in the RPM's.

Anyone care to comment?  Any chance of getting this into FC5?

Alan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFDi+YcCfroLk4EZpkRAt0lAJ9d7qa2OgejRurZmRKjk8BoSe6vJwCeOmCd
ZCDhuyr1t2IkljN+u96wgSA=
=JPhx
-----END PGP SIGNATURE-----