On Tue, Jul 06, 2004 at 04:41:08PM -0400, seth vidal wrote: > On Tue, 2004-07-06 at 16:39, Florin Andrei wrote: > > I would like to configure yum so that it will only update packages with > > updates from their own repositories of origin. [...] > > Is that currently achievable with yum? > > no and tracking an installed package back to it's repository of origin > is going to be prone to failure. Well ... there is the MD5 which should be an okay unique ID, but in general what Florin ask is his own view of the constraints but there are others (for example you may want to pick the -devel or -debuginfo packages from the same source, or make sure that your mod_xxx packages come from the same source as your apache). I'm firmly convinced that trying to handle a large set of heterogenous sources with conflicts in a totally automated fashion does not work, you will have to provide policies to resolve conflicts. One policy is to hierarchise sources and order them so that all packages can be sorted by priority order and update/upgrade would only pick teh first match in that list. Other policies are possible for example stating that all packages requiring (directly or indirectly) apache should come from a given source. Trying to provide easy way to plug policies in the engine sounds to me a far more productive way to spend the developpers limited time ... Daniel -- Daniel Veillard | Red Hat Desktop team http://redhat.com/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
