I see several packages have constructs like: Depends: openssl-shlibs | openssl097-shlibs BuildDepends: openssl-dev | openssl097-dev
This is not correct--if, for example, one has openssl097-dev installed at build-time, then one *must* have openssl097-shlibs at run-time (openssl-shlibs will not suffice). A quick check of the crypto branch of the 10.3 and 10.2-gcc3.3 trees finds: 10.3: stable/crypto/finkinfo/stunnel4.info unstable/crypto/finkinfo/dcmtk-ssl.info unstable/crypto/finkinfo/net-snmp-ssl.info unstable/crypto/finkinfo/stunnel4.info 10.2-gcc3.3: unstable/crypto/finkinfo/ettercap-ssl-0.6.9-12.info unstable/crypto/finkinfo/net-snmp-ssl.info What's our current thought on us changing these and telling $Maintainer the situation vs. telling them to fix their packages and waiting for them to do so? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
