Geek Answers Handbook

Set dependency for package from EPEL in spec file

I am writing a specification file for software that depends on php-mcrypt. My target OS is CentOS 6.5 php-mcryptnot in the repositories CentOS, but is in EPEL. Is there a better way to satisfy this dependency on a string Requires:, rather than manually install EPELin %pre? I really don’t like the idea of ​​forcing another repo to be installed in RPM, but I also don’t like it when RPMI can’t install a more dependent one, which does not seem to exist until someone dies to start searching through various foreign repositories.

What is the best way to handle this?

+4
source share
1 answer

I do not know a better way to indicate this particular part in a line Requires.

The only thing you could do, besides your suggestions, would also be to depend on a package epel-releasethat would at least give them a more specific hint in the right direction. The only problem / disadvantage of this is that you depend on the fact that they installed this package / repo instead of just installing the package EPEL php-mcryptyourself / etc.

0
source

More articles:


All Articles