On Tue, Sep 27, 2016 at 10:53 PM, Björn Esser <[email protected]> wrote: > > Forgot to mention: Explicit dependencies are usually the better way, > instead of relying on implicit dependencies… >
Of course. > File Dependencies > RPM gives you the ability to depend on files instead of packages. Whenever > possible you should avoid file dependencies as they slow down dependency > resolution and require the package manager to download file lists in addition > to to regular dependency information. There are, however, times when other > technical considerations outweigh these considerations. If the files you need > are prone to moving between packages of different names, it can be useful to > depend on those files directly. I found that a dependency on "setup" package is not common practice: # dnf repoquery --whatrequires setup|wc -l 19 -- WBR, Roman Tsisyk <[email protected]> _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
