From: "Clément Lassieur" <clement@lassieur.org>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: Unrar package might contain proprietary code.
Date: Wed, 01 Mar 2017 21:39:03 +0100 [thread overview]
Message-ID: <87fuiwn34o.fsf@lassieur.org> (raw)
In-Reply-To: <20170301202009.GA22689@jocasta.intra>
> 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)
This is what I was referring to:
Whichever license you plan to use, the process involves adding two
elements to each source file of your program: a copyright notice (such
as “Copyright 1999 Terry Jones”), and a statement of copying permission,
saying that the program is distributed under the terms of the GNU
General Public License (or the Lesser GPL).
To me it is pretty clear. And it is not only about GNU programs.
> 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?
> 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.
But the site could be mistaken too.
next prev parent reply other threads:[~2017-03-01 20:39 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuiwn34o.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.