Re: [Rdo-list] Why use yum priority in rdo-release repo file?
On 20/06/13 14:15, Sandro "red" Mathys wrote:
On Thu, Jun 20, 2013 at 1:56 PM, Matthias Runge
<mrunge(a)redhat.com
<mailto:mrunge@redhat.com>> wrote:
On 20/06/13 13:50, Sandro "red" Mathys wrote:
> Great, thanks for the quick reply and the quick fix. Still thinking
> yum priorities are bad and should be removed completely from RDO
> (RHOS is a different story) but if only directly openstack related
> packages remain in the repo, it shouldn't matter anyway. -- Sandro
>
Why do you think priorities are bad?
Because they are patronizing the user, relatively hard to overcome and
situations where they seem necessary should be avoided in general.
Yum does not resolve dependencies very well, when it comes to ambiguities.
Simple example: we're using Django14 in RDO, whereas EPEL has both, and
the same versions.
yum prioritizes packages with shorter names, thus would install Django
instead of Django14. (version 1.3 vs. 1.4).
Other example: You could have a version of a software which is just a
plain "community" version, whereas you could have in RDO a more
"supported" version, e.g expressed by other logos etc, but still the
same package version.
Like in what case? When will RDO ever want an older version of something
than what is in RHEL / EPEL?
Good question: what will be priorized? Higher prio repo or higher
package version?
The only thing I can possibly come up with right now are the kernel and
other tools where new networking stuff (netns, maybe more) was enabled
ahead of time but I sure hope those changes make it back into RHEL with
the next kernel update there. Or if not, that new RHEL kernels are again
re-built with those patches for RDO as well to avoid security holes.
Good to see, you have found a use-case.
Matthias