libnessus3-ssl is marked as Restrictive (links to OpenSSL) and the source is now unavailable upstream (license change for newer versions and dead FTP server). fink fetch libnessus3-ssl then fails to build, only checking Source: defined in the .info file.
However, the tarball _is_ available from <http://distfiles.master.finkmirrors.net/>, probably because of libnessus3 (non-ssl). This brings up some questions: 1) Should packages marked as Restrictive be able to check mirrors if they can't find the source upstream? 2) Should a new license option be used for packages marked as restrictive because of OpenSSL linkage (or other similar situation)? Fink policy says "will not distribute binaries", but in practice this also means that the source tarball is not distributed/mirrored. Most packages that fall into this category are GPL, so the source alone can be distributed. Having a new License option, Restrictive/SourceOnly for example, to complement Restrictive/Distributable would take care of these packages. Hanspeter ------------------------------------------------------------------------------ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
