-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Thu, 2017-04-06 at 12:40 +0100, Richard W.M. Jones wrote: > I have a package which needs GNU Privacy Guard (GPG) at runtime. It > can either run gpg (v1) or gpg2, as it uses a subset of the features > supported by both, and the program searches for both binaries. > > The natural way to express this as an RPM dependency would be: > > Requires: (gnupg or gnupg2) > > Unfortunately this is forbidden by the packaging rules: > > https://fedoraproject.org/wiki/Packaging:Guidelines#Rich.2FBoolean_ > dependencies > > (BTW the link in that section is wrong - it should go to: > http://rpm.org/user_doc/boolean_dependencies.html ) > > This admonition was added in: > > https://fedoraproject.org/w/index.php?title=Packaging:Guidelines&di > ff=prev&oldid=441810 > > What's not explained is why, except that it "causes issues with the > package updates process". It seems as if the or-rule above would be > simple enough, so what's the exact problem? None (or almost none) of rel-eng (and probably some other critical tools) are not supporting them. For example, "mash" uses yum which just crashes when finds out rich dependency. Other tools are doing their own depsolving which leads to the wrong results or non-solvable dependencies. I've heard somewhere that rel-eng are planning to port their tools to DNF for F27 which should improve situation. Also I did some improvements recently in this direction in libdnf (and backported to hawkey). But looks like only few people are interested in using rich dependencies... Getting a bit back to the original problem, just put Req: gnupg2 since gnupg (v1) is basically dead (and RPM uses gnupg2 anyway). > > Rich. > - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAljmLdYACgkQaVcUvRu8 X0xi5w//ZLPft1gsshJcK0mTRxRWLDGentLZ+RV/QjLZzCsFpf2LB76EkMdEg9xC M+B8ZGAdfxsqPc1m2xvy/iXt33PhUy2xODHp1D/qFgUUtt9Bucr7Tx+uWgnoB4Lz tFKmOfa4cux+h7+TLlw0snVGDcHGbIZlWg/EJrCk1jy1Aaj8cpPh0LFuOWvmTP8t 69zjpVHux4uCMf5kF0M3yem0Db2gFsir7w2FBMSHmFUZS4S9E6Ap655tLrC7gBve v8crsS+O7igk0lIMClwNI7iFl7QJdJq96qxWa8+HMtz1yme0+g/3PKqPubYWApQA CF7zqSmAiDRWZCoVZ6+IX0YeDQ20tkzmIL6bfSUigt9CKhZVvoHMA1oLCczSh3xj h6QMceziATcI91VL/0KUairDhyh2NYzL9lHnrx1Fe7CGCy+VuJT4FyzDZ3AcQ2bQ 3pCiqyb21/WsFza20zNZL21ltbHXiNPdXl7GnZ2C2RihGUAFUBYsQQ/vFtKj0R4y afEbPFaPV0C9HrawzRsfVZxiquGPXWwwbgNpZFyuQrtpOZFlrKpVxOQoWOmt/vAg dZmoddqAjnVPwpFJlW5BcvwI/Akuu2EvSmfFsQ2YVBEzfkhsYLYBXwzPnxu4BAdk DhqDwVEP7zXCkPEbK76GS/9ipRnWE/vpz/47xU2UTaWVhgR8AT8= =R55y -----END PGP SIGNATURE----- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
