Hi Russ,

Russ Allbery wrote:
> > neither inside /usr/share/common-licenses/Artistic nor in
> > /usr/share/doc/base-files/README nor in
> > /usr/share/doc/base-files/changelog.gz is declared (or even hinted)
> > which version or variant of "The Artistic License" is shipped in
> > /usr/share/common-licenses/Artistic.
> 
> > According to https://spdx.org/licenses/ there are at least five
> > registered versions and variants of the Artistic License:
> 
> >   * Artistic License 1.0
> >   * Artistic License 1.0 (Perl)
> 
> What does SPDX think the difference between these two is?

Actually quite a lot. :-(

Artistic-1.0.txt Artistic-1.0-cl8.txt only differ in that added 8th
clause. But Artistic-1.0-Perl.txt differs more from both -- and seems
to also include that new 8th clause, slightly modified, too.

Niko Tyni noticed on IRC yesterday evening that there are at least two
different variants of the "Artistic License" because of the different
number of clauses (9 vs 10). I digged deeper after that comment and
this bug report is the result of that digging.

Here's the wdiff (as a normal diff doesn't help much on changed words.
Piping it through colordiff helps a lot, otherwise look for the
strings "[-" and "{+". It's based on a checkout of
http://git.spdx.org/?p=license-list.git

→ wdiff Artistic-1.0.txt Artistic-1.0-Perl.txt | colordiff
The [-Artistic License-] {+"Artistic License"+}

Preamble

The intent of this document is to state the conditions under which a Package 
may be copied, such that the Copyright Holder maintains some semblance of 
artistic control over the development of the package, while giving the users of 
the package the right to use and distribute the Package in a more-or-less 
customary fashion, plus the right to make reasonable modifications.

Definitions:

     "Package" refers to the collection of files distributed by the Copyright 
Holder, and derivatives of that collection of files created through textual 
modification.

     "Standard Version" refers to such a Package if it has not been modified, 
or has been modified in accordance with the wishes of the Copyright [-Holder.-] 
{+Holder as specified below.+}

     "Copyright Holder" is whoever is named in the copyright or copyrights for 
the package.

     "You" is you, if you're thinking about copying or distributing this 
Package.

     "Reasonable copying fee" is whatever you can justify on the basis of media 
cost, duplication charges, time of people involved, and so on.  (You will not 
be required to justify it to the Copyright Holder, but only to the computing 
community at large as a market that must bear the fee.)

     "Freely Available" means that no fee is charged for the item itself, 
though there may be fees involved in handling the item. It also means that 
recipients of the item may redistribute it under the same conditions they 
received it.

1. You may make and give away verbatim copies of the source form of the 
Standard Version of this Package without restriction, provided that you 
duplicate all of the original copyright notices and associated disclaimers.

2. You may apply bug fixes, portability fixes and other modifications derived 
from the Public Domain or from the Copyright Holder.  A Package modified in 
such a way shall still be considered the Standard Version.

3. You may otherwise modify your copy of this Package in any way, provided that 
you insert a prominent notice in each changed file stating how and when you 
changed that file, and provided that you do at least ONE of the following:

     a) place your modifications in the Public Domain or otherwise make them 
Freely Available, such as by posting said modifications to Usenet or an 
equivalent medium, or placing the modifications on a major archive site such as 
[-ftp.uu.net,-] {+uunet.uu.net,+} or by allowing the Copyright Holder to 
include your modifications in the Standard Version of the Package.
     b) use the modified Package only within your corporation or organization.
     c) rename any non-standard executables so the names do not conflict with 
standard executables, which must also be provided, and provide a separate 
manual page for each non-standard executable that clearly documents how it 
differs from the Standard Version.
     d) make other distribution arrangements with the Copyright Holder.

4. You may distribute the programs of this Package in object code or executable 
form, provided that you do at least ONE of the following:

     a) distribute a Standard Version of the executables and library files, 
together with instructions (in the manual page or equivalent) on where to get 
the Standard Version.
     b) accompany the distribution with the machine-readable source of the 
Package with your modifications.
     c) [-accompany any non-standard executables with their corresponding 
Standard Version executables, giving the-] {+give+} non-standard executables 
non-standard names, and clearly [-documenting-] {+document+} the differences in 
manual pages (or equivalent), together with instructions on where to get the 
Standard Version.
     d) make other distribution arrangements with the Copyright Holder.

5. You may charge a reasonable copying fee for any distribution of this 
Package.  You may charge any fee you choose for support of this Package.  You 
may not charge a fee for this Package itself.  However, you may distribute this 
Package in aggregate with other (possibly commercial) programs as part of a 
larger (possibly commercial) software distribution provided that you do not 
advertise this Package as a product of your own.  {+You may embed this 
Package's interpreter within an executable of yours (by linking); this shall be 
construed as a mere form of aggregation, provided that the complete Standard 
Version of the interpreter is so embedded.+}

6. The scripts and library files supplied as input to or produced as output 
from the programs of this Package do not automatically fall under the copyright 
of this Package, but belong to [-whomever-] {+whoever+} generated them, and may 
be sold commercially, and may be aggregated with this Package.  {+If such 
scripts or library files are aggregated with this Package via the so-called 
"undump" or "unexec" methods of producing a binary executable image, then 
distribution of such an image shall neither be construed as a distribution of 
this Package nor shall it fall under the restrictions of Paragraphs 3 and 4, 
provided that you do not represent such an executable image as a Standard 
Version of this Package.+}

7. C [-or perl-] subroutines {+(or comparably compiled subroutines in other 
languages)+} supplied by you and linked into this Package {+in order to emulate 
subroutines and variables of the language defined by this Package+} shall not 
be considered part of this [-Package.-] {+Package, but are the equivalent of 
input as in Paragraph 6, provided these subroutines do not change the language 
in any way that would cause it to fail the regression tests for the language.+}

8. {+Aggregation of this Package with a commercial distribution is always 
permitted provided that the use of this Package is embedded; that is, when no 
overt attempt is made to make this Package's interfaces visible to the end user 
of the commercial distribution.  Such use shall not be construed as a 
distribution of this Package.

9.+} The name of the Copyright Holder may not be used to endorse or promote 
products derived from this software without specific prior written permission.

[-9.-]{+10.+} THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR 
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF 
MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.

The End

> The original Artistic License was the one that shipped with Perl, so
> I'm confused about what the difference would be.

Actually I'm slightly confused, too, because that's the way I had it
in mind, too. That's why I opened pandora's box to have it clarified.
:-)

> > Please clearly state inside the file
> 
> We should not modify the license texts included in common-licenses.

Ok. And renaming the file is obviously a bad idea, too, I know. That's
why I didn't ask for that. :-)

A properly named symlink may have some value, though.

> There's no harm in spelling out which one is intended in README, though.

That would already help IMHO.

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to