From: Alex Vong <alexvong1995@gmail.com>
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: Thu, 02 Mar 2017 09:45:50 +0800 [thread overview]
Message-ID: <87varscuy9.fsf@gmail.com> (raw)
In-Reply-To: <87d1e0n18g.fsf@lassieur.org> ("Clément Lassieur"'s message of "Wed, 01 Mar 2017 22:19:59 +0100")
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
Clément Lassieur <clement@lassieur.org> writes:
>>> 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.
>>
>> Or if the resultant work is illegal?
>
> Actually, unrarlib is dual-licensed, so it is possible to use it within
> a proprietary program (see http://www.unrarlib.org/license.html).
>
> But I'll trust you that COPYING is enough :) Sorry for bothering you
> then.
>
> Clément
I think Debian considered it to be non-free, see the package page[0] and
the copyright page[1].
However, 'unar'[2] can also extract rar files and is free
software[3]. It is on my TODO list. (But I am busy studying right now
and the program uses gnustep which is something I am not familiar with.)
John, if you like you can look into it.
[0]: https://packages.debian.org/sid/unrar
[1]: http://metadata.ftp-master.debian.org/changelogs/non-free/u/unrar-nonfree/unrar-nonfree_5.4.5-1_copyright
[2]: https://packages.debian.org/sid/unar
[3]: http://metadata.ftp-master.debian.org/changelogs/main/u/unar/unar_1.10.1-1_copyright
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-03-02 1:46 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
2017-03-01 20:39 ` Clément Lassieur
2017-03-01 21:19 ` Clément Lassieur
2017-03-02 1:45 ` Alex Vong [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87varscuy9.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.