On Nov 15, 2006, at 2:44 PM, David Reiser wrote: > I've been wrangling with gnucash dependencies for a while. Early on > it was possible to avoid the crypto tree by getting unified versions > of libofx and crypt-ssleay-pm packaged. > > Gwenhywfar and aqbanking will be crypto for the foreseeable future > because they implement the crypto for the German hbci banking. > > When I submitted the info files to the tracker, I had handled the ssl > dependencies in gwen and aqbanking the same way as they were handled > in libofx and crypt-ssleay: forcing the use of the system openssl > libraries. > > Considering that the main use of gwen and aqbanking will be gnucash, > is it appropriate to restrict gwen and aqbanking to the system > openssl versions (so that all use of ssl in a fully enabled gnucash > goes through the system versions), or should the dependency be > softened to allow the fink openssl versions?
If a package is licensed under the GPL without an exception, it may not be linked to fink's openssl, end of story. So, no, the restriction should not be "softened", you ned to use the libssl and libcrypto that ship with the OS. However, if the packages have a GPL exception allowing openssl, then it is okay. Peter ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
