From: John Darrington <john@darrington.wattle.id.au>
To: Cl??ment Lassieur <clement@lassieur.org>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: Unrar package might contain proprietary code.
Date: Wed, 1 Mar 2017 21:20:09 +0100 [thread overview]
Message-ID: <20170301202009.GA22689@jocasta.intra> (raw)
In-Reply-To: <87h93cn4ye.fsf@lassieur.org>
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
On Wed, Mar 01, 2017 at 08:59:37PM +0100, Cl??ment Lassieur wrote:
I had a look at the source of the recently commited "unrar" package, and
I could not find neither "copyright" lines nor pointers to the full
notice, except in unrarlib.h and unrarlib.c, which belong to a different
project. IANAL, but according to GPLv2 and
https://www.gnu.org/licenses/gpl-howto.en.html, those things are
mandatory, COPYING is not enough. So I think the "unrar" package
contains proprietary code.
I think you are mistaken.
Yes, the package does not explicitly have headers in the way that GNU recommends.
But I do not see how such a recommendation is "mandatory". (It's mandatory for
gnu programs, but there are many non-gnu programs in Guix)
The placement of COPYING - whilst normally not all that we would like - is
part performance of an intent to licence the software.
Like you say, the authors have taken GPL code from another project and incorporated
it into unrar - that is only possible if the the resultant work is GPL compatible.
Also if you look at the site where it is hosted https://gna.org/projects/unrar you
will see that it says: License: GNU General Public License V2 or later.
So, whilst it has been poorly executed, I believe there is ample evidence that this
program is licenced GPL.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-03-01 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 19:59 Unrar package might contain proprietary code Clément Lassieur
2017-03-01 20:20 ` John Darrington [this message]
2017-03-01 20:39 ` Clément Lassieur
2017-03-01 21:19 ` Clément Lassieur
2017-03-02 1:45 ` Alex Vong
2017-03-02 1:49 ` Leo Famulari
2017-03-02 5:54 ` John Darrington
2017-03-02 6:13 ` John Darrington
2017-03-02 10:56 ` Alex Vong
2017-03-02 12:51 ` Ricardo Wurmus
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=20170301202009.GA22689@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.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).