updates in builders?

Kevin Fenzi kevin at tummy.com
Mon Dec 10 20:11:53 UTC 2007

We may have in fact discussed this before in the past, but I don't know
if we ever came to any decision on it. 

Should the builders build against just the base stock OS, or 
should they also pull in the released updates?

The reason this came up is firefox. 

RHEL 5.0 stock comes with a firefox that provides gecko-libs version The latest updates have a firefox that provides gecko-libs

So, if we build an app against base only, anyone with updates will not
be able to use it or update until they remove it. 

If we build against updates as well then they will be forced to apply
the dependent packages from updates. 

Personally, my vote is to always add the updates in. 
It's easier to tell people that they must have an updated system in
order to use EPEL packages. 

Any other thoughts?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/epel-devel-list/attachments/20071210/201cf0c9/attachment.sig>

More information about the epel-devel-list mailing list