unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: Help identifying licenses
Date: Sun, 06 Oct 2019 13:59:39 -0600	[thread overview]
Message-ID: <794d0849ae37841598b32f872ad27cb9abf2c859.camel@gmail.com> (raw)
In-Reply-To: <874l0llmzb.fsf@nckx>

On Sun, 2019-10-06 at 20:58 +0200, Tobias Geerinckx-Rice wrote:
> Tobias Geerinckx-Rice 写道:
> > As noted on IRC: I've mirrored that file from a debian 
> > system[0]. What
> > a mess: it's *almost*
> > <https://directory.fsf.org/wiki/License:Clarified_Artistic_License_1.0>,
> > but not actually the same (e.g. points 3.e & 4.e are missing).
> > 
> > Considering this is what Debian calls the ‘Artistic’ licence, 
> > though,
> > we can be almost certain that other Guix packages have the same 
> > subtle
> > difference already.
> 
> It turns out that what text I had found on-line as the ‘Artistic 
> 1.0’ licence was either bogus or mislabelled.  It does seem to be 
> the (non-free!) Artistic 1.0 licence.
> 
> Kind regards,
> 
> T G-R


As mentioned on IRC, The non-free artistic license the FSF links to and says
is too vague does not have an identical clause 8. OSI calls it the perl
version of artistic-1.0. I do not think FSF has looked at it.

Kenny was added to the filters git repo with its license note Feb 20 2006.
Has the license at the specified location been changed since then?

I will contact the copyright holders and see if they are willing to use
clarified-artistic or artistic-2.0 or disjunct artistic/gpl or some other
free license. If so, I will ask the package maintainer to change
debian/copyright with that detail. Until then, I will make sure the package
does not install or use kenny.
-- 
-Jesse

      reply	other threads:[~2019-10-06 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 17:55 Help identifying licenses Jesse Gibbons
2019-10-06 18:56 ` Tobias Geerinckx-Rice
2019-10-06 18:58   ` Tobias Geerinckx-Rice
2019-10-06 19:59     ` Jesse Gibbons [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=794d0849ae37841598b32f872ad27cb9abf2c859.camel@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).