[MacPorts] snc/licenses modified

MacPorts noreply at macports.org
Fri Aug 14 07:23:31 PDT 2009


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

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: snc/licenses
=========================================================================
--- snc/licenses (version: 1)
+++ snc/licenses (version: 2)
@@ -9,13 +9,17 @@
 }}}
 '''NOTE:''' this field is purely for informational purposes.
 
-Since there are no predetermined values to use with {{{license}}} it is suggested that we follow [http://www.finkproject.org/doc/packaging/policy.php#licenses Fink's approach].  To that end, here are the licenses I feel accomplish the majority of features used in Fink's licensing system when viewing from our eventual goals of automated builds and distribution of binaries.
+Since there are no predetermined values to use with {{{license}}} it is suggested that we follow [http://www.finkproject.org/doc/packaging/policy.php#licenses Fink's approach].  To that end, here are the licenses with my commentary on how I feel they accomplish the eventual goals of automated builds and distribution of binaries.
 == GPL ==
-The GNU [http://www.gnu.org/licenses/gpl.html General Public License]. This license requires that the source is available from the same place as the binary.
+The GNU [http://www.gnu.org/licenses/gpl.html General Public License] has two important aspects: distribution and use.
+
+The GPL requires that source code is available from the same place as the binary, which is presently handled by MacPorts since it provides binaries by building them from the source (by default).  In the future, it may become necessary to download both a binary and source code for ports using this license or to have the source code bundled with the archive of the binary.
+
+The license further stipulates that the library generated from the code can only be used in free projects.  Since MacPorts only handles open-source software, this aspect is not a problem.
 == LGPL ==
-The GNU [http://www.gnu.org/licenses/lgpl.html Lesser General Public License]. This license requires that the source is available from the same place as the binary.
+The GNU [http://www.gnu.org/licenses/lgpl.html Lesser General Public License] differs from the GPL by allowing generated libraries to be used in proprietary programs.  MacPorts sees these licenses as identical since we only deal with open-source software. As such, I don't believe we need this category.
 == GPL/LGPL ==
-This if a special case for packages where one part is licensed under the GPL (e.g. the executables) and another part is licensed under the LGPL (e.g. the libraries).
+This if a special case for packages where one part is licensed under the GPL (e.g. the executables) and another part is licensed under the LGPL (e.g. the libraries). I cannot find this being an important case for MacPorts as they are treated the same in MacPorts; we don't need this category.
 == BSD ==
 For BSD-style licenses. This includes the so-called "original" BSD license, the "modified" BSD license and the MIT license. The Apache license also counts as BSD. With these licenses the distribution of source code is optional.
 == Artistic ==

-------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 .


More information about the macports-changes mailing list