[Server-devel] Creating a spin - any mechanisms around $product-release, $product-release-notes, $product-logos packages...?

[Martin Langhoff]

I'm finishing off the F9 port of the OLPC School Server, and as part
of that I'm preparing xs-release, xs-release-notes and xs-logos
packages.

As far as I can see, these are pulled because they provide
system-release and system-logos. fedora-release-notes is pulled in by
fedora-release, and perhaps by something depending on indexhtml
(httpd?).

My key question is: will anything in the Fedora machinery (anaconda,
rpm, yum) be looking for a magic "product" name, and then try to use
it to request $product-release?

(I ask to be safe - recently got very confused by anaconda not
upgrading Fedora-based spins due to mismatching 'product' between
.discinfo and /etc/redhat-release . Knowing these special rules is
important ;-) and I have not found yet any document laying out the
subtle traps awaiting anyone doing a Fedora derivative as I am
doing...)

cheers,


m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff