Let's pick a really cool package that currently exists in
redhat.
Severn currently includes spamasssassin 2.55.
Those crazy SA guys are coding up 2.6. When they release 2.6 they usually
release a rpm package.
So one of the SA developers will contact redhat and tell them to include
their rpm in the severn version of redhat?
I can't give an authorative answer, but this is not the way it was
meant to work, AFAIK. An external person should be *responsible*
for a package and has to comply with RH guidelines etc. In my
experience, "standard" rpm's released by projects are in general
much different w.r.t. packaging style.
So, "contact redhat and tell them to include their rpm in ..." does
sound a bit different, as it doesn't sound like actively working with
RH standards and guidelines and/or continous responsiblity etc. (but
maybe you thought of something else).
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204