Transition of packages from system-openssl-dev

"Hanspeter Niederstrasser" <[email protected]>
Newsgroups gmane.os.apple.fink.devel
Message-ID <[email protected]>
Dear Fink Developer,

As you may be aware, OS X 10.11 does not provide a full install of OpenSSL
in /usr (it only has the dylib, but not the headers). Therefore, the
package system-openssl-dev is no longer available on 10.11.  To fill this
dependency gap, packages must transition to a Fink package that provides
SSL functionality (like openssl100 or gnutls28). I've added a list of all
packages that are currently using system-openssl-dev in the 10.9-libcxx
tree to the Fink wiki:

http://wiki.finkproject.org/index.php/Fink:Policy:system-openssl#Deprecation_of_system-openssl-dev

Because the (L)GPL and OpenSSL licenses are incompatible, any package that
is switched to use openssl100-shlibs must change its License field.  The
current (as of fink-0.39.1) policy is to use "Restrictive".  However,
there is code in the Fink pipeline that will allow the new license strings
"GPL/OpenSSL" and "LGPL/OpenSSL" to better identify those packages. Once
that code is released, (L)GPL packages linking to OpenSSL can use the
relevant entry.

If your package is not licensed under a (L)GPL license, you do not need to
change the License: field.  However, the package must still be updated to
no longer use system-openssl-dev on at least 10.11.

Lastly, packages linking to a cryptography library do not need to be moved
to the crypto directory in CVS.  Crypto is reserved for those packages
that actually implement cryptography.

Hanspeter

-- 
More agile than a turtle, stronger than a mouse, nobler than a lettuce.


------------------------------------------------------------------------------
_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.