On Sat, Aug 11, 2018 at 8:07 PM Rex Dieter <rdie...@math.unl.edu> wrote:
> Robert Marcano wrote:
> > For example, someone developing against krb5-devel for a GSSAPI client,
> > probably doesn't need openssl-devel installed, that they are linking
> > against Kerberos doesn't means they use the same crypto library
> > directly, they could use nss for example.
> I think you're most likely going to need to deal with this on a
> basis. In this specific example, find out for sure if "probably doesn't
> need openssl-devel" is entirely accurate or not, and take appropriate
Not sure a case-by-case basis will always work, for example I force removed
compat-openssl10-devel (rpm - e compat-openssl10-devel --nodeps) that is
pulled by nodejs-devel, and I am able to link against NodeJS libraries,
because the modules I need to build doesn't use OpenSSL. So
compat-openssl10-devel should not be a hard dependency for nodejs-devel.
Sadly the package maintainer think this is fine .
A small packaging guideline change about reducing *-devel hard dependencies
when they aren't always required could help.
devel mailing list -- email@example.com
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines