[MacPorts] snc/licenses modified

[MacPorts]

Changed page "snc/licenses" by snc at macports.org from 129.137.118.253*
Page URL: <http://trac.macports.org/wiki/snc/licenses>
Diff URL: <http://trac.macports.org/wiki/snc/licenses?action=diff&version=15>
Revision 15

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: snc/licenses
=========================================================================
--- snc/licenses (version: 14)
+++ snc/licenses (version: 15)
@@ -15,7 +15,7 @@
 
 While we want to simply make use of licensing information, we should also beware of instances where it is incorrect. For example, as long as the LGPL is distributed along with any packages that may be utilizing such libraries, it should be okay. If they are not provided by the package, then that package is violating the LGPL. In this instance we should not build binaries. Instead, we ought to report such cases to the vendor or to the FSF so the licenses can be fixed before trying to distribute said software.
 
-To most easily prevent us from distributing unauthorized binaries we should only build them if the license is of a suitable level of openness. That is, our automation system must be able to address the concerns of the license before any packages using that license should be distributed as binaries.
+Our back end systems must be able to address the concerns of the license before any packages using that license should be distributed as binaries. This means we will never distribute binaries of commercial licenses software nor distribute packages that require their license to accompany the binary until we have infrastructure for doing so.
 
 Since there are no predetermined values to use with {{{license}}} I suggest that we divide software into categories.  To that end, here are the categories and subsequent licenses I feel accomplish the eventual goals of automated builds and distribution of binaries.
 
@@ -33,13 +33,13 @@
 
 As a general rule, every package that is to be distributed as a binary must contain a copy of its license and any accompanying notices. This is usually handled with Makefiles automatically placing it along with the documentation. Of interesting note is the fact that many packages have man pages that cover the license as well. 
 
- * Apache
+ * [#BSD Apache]
  * [#BSD BSD]
  * Common Development and Distribution License
  * Eclipse Public License
  * [#GPL GPL]
  * [#LGPL LGPL]
- * MIT
+ * [#BSD MIT]
  * MPL
 
 == GPL ==

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on snc/licenses. If it was not you, please
report to .