Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have following packages, built by my RPM spec:

libevent backend

%package -n libfoo-libevent
Summary: libevent backend for FOO
Provides: libfoo-backend
Requires: libevent >= 1.4

libev backend

%package -n libfoo-libev
Summary: libev backend for FOO
Provides: libfoo-backend
Requires: libev >= 3

And the library itself which requires at least one backend installed (both of them also OK)

%package -n libfoo
Summary: FOO library
Requires: libfoo-backend

Question: How can I control the order in which the backend will be selected by default when I'm installing it with yum install libfoo. Currently it seems like it is sorting list ["libfoo-libevent", "libfoo-libev"] alphabetically and always picks libfoo-libev. Is there any way to make libfoo-libevent preferred (except renaming it of course)

share|improve this question
Why is this relevant in your case? – Nils Jun 11 '13 at 21:15
because I have requirement that "libfoo-libevent" backend should be chosen as default. the googling says that it isn't controlled. repoquery --whatprovides MTA also shows alphabetically ordered results. What I need some field to put higher priority to "libfoo-libevent" over "libfoo-libev" – avsej Jun 11 '13 at 21:43

One approach is to put libfoo-libevent and libfoo-ev into different repositories and then use yum priorities. Unfortunately priorities are assigned per-repository, not per-package.

share|improve this answer
that's does not seem like good option :) – avsej Feb 9 '15 at 15:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.