unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Calibre
Date: Tue, 17 Feb 2015 21:30:56 +0100	[thread overview]
Message-ID: <20150217203056.GB30365@debian> (raw)
In-Reply-To: <87lhjx871z.fsf@netris.org>

On Tue, Feb 17, 2015 at 12:02:00AM -0500, Mark H Weaver wrote:
> The calibre source tarball contains non-free software.  Debian
> distributes their own excerpted source tarball instead, with the
> src/unrar, src/calibre/ebooks/markdown, and resources/viewer/mathjax
> directories removed, as well as src/odf/thumbnail.py.

Amazing, thanks for looking into it. How do you find out which files
debian drops? I suppose that a "dfsg" in the package name is a warning
sign? This is even more surprising as there is the file COPYRIGHT
in the distribution, which diligently lists the licenses of lots of
packages, except apparently for the non-free ones... I will try
to contact the upstream author.

> (1) src/unrar's license includes the following clause:
> 
> --8<---------------cut here---------------start------------->8---
>    2. UnRAR source code may be used in any software to handle
>       RAR archives without limitations free of charge, but cannot be
>       used to develop RAR (WinRAR) compatible archiver and to
>       re-create RAR compression algorithm, which is proprietary.
>       Distribution of modified UnRAR source code in separate form
>       or as a part of other software is permitted, provided that
>       full text of this paragraph, starting from "UnRAR source code"
>       words, is included in license, or in documentation if license
>       is not available, and in source code comments of resulting package.
> --8<---------------cut here---------------end--------------->8---
> 
>     This restriction on use makes it non-free software.

Clearly so!

> (2) src/calibre/ebooks/markdown/serializers.py license includes the text:
> 
> --8<---------------cut here---------------start------------->8---
>   # By obtaining, using, and/or copying this software and/or its
>   # associated documentation, you agree that you have read, understood,
>   # and will comply with the following terms and conditions:
>   #
>   # Permission to use, copy, modify, and distribute this software and
>   # its associated documentation for any purpose and without fee is
>   # hereby granted, provided that the above copyright notice appears in
>   # all copies, and that both that copyright notice and this permission
>   # notice appear in supporting documentation, and that the name of
>   # Secret Labs AB or the author not be used in advertising or publicity
>   # pertaining to distribution of the software without specific, written
>   # prior permission.
> --8<---------------cut here---------------end--------------->8---
> 
>     I'm not as confident that this one is a problem, partly because I
>     guess it is probably unenforceable, but the first paragraph is
>     attempting to put a restriction on use.  They are saying that you're
>     not even allowed to use this software unless you have "read,
>     understood, and will comply with ...".

I suppose that the first sentence merely states "the following license
is valid", so I do not think it is a real problem. One always needs to
comply with the license, no?

> (3) src/odf/thumbnail.py simply says "License: Freeware".  I have no
>     idea what that means.  It is "Non-functional Data" (an image), so
>     (quoting the GNU FSDG) "It can be included in a free system
>     distribution as long as its license gives you permission to copy and
>     redistribute, both for commercial and non-commercial purposes."
>     However, I don't think we can deduce that from "License: Freeware".

I think it is supposed to mean "public domain", but that is just guessing.
We should drop the file.

I will try to take out 1) and 3); I am not sure about 2), though.
As usual in python, I suppose that things will still compile and install,
and then one just needs to hope that it still works.

Andreas

  reply	other threads:[~2015-02-17 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 10:20 Calibre Andreas Enge
2015-02-17  4:23 ` Calibre Mark H Weaver
2015-02-17 20:21   ` Calibre Andreas Enge
2015-02-17  5:02 ` Calibre Mark H Weaver
2015-02-17 20:30   ` Andreas Enge [this message]
2015-02-17 21:35     ` Calibre Mark H Weaver
2015-02-17 21:50       ` Calibre Andreas Enge
2015-02-17 22:09         ` Calibre Mark H Weaver
2015-02-17 22:17     ` Calibre Andreas Enge

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=20150217203056.GB30365@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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