From: Andreas Enge <andreas@enge.fr>
To: Nikita Karetnikov <nikita@karetnikov.org>, bug-guix@gnu.org
Subject: Re: [PATCH] distro: Add rsync
Date: Fri, 21 Dec 2012 14:17:58 +0100 [thread overview]
Message-ID: <201212211417.58622.andreas@enge.fr> (raw)
In-Reply-To: <87zk17613l.fsf@karetnikov.org>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Am Freitag, 21. Dezember 2012 schrieb Nikita Karetnikov:
> 1. Change 'uri' according to this [1] example.
What does this change? Especially as it is not done systematically
for the files already in the distribution.
> 2. Use a single semicolon after expression. [2]
Okay, thanks.
> 3. It's probably better to say what licenses are used for the other
> files.
Actually, what is one expected to do concerning licenses?
README says:
"Rsync may be used, modified and redistributed only under the terms of
the GNU General Public License, found in the file COPYING in this
distribution"
COPYING is GPLv3. So I checked a few files whether this means
gpl3 or gpl3+.
rsync.c states gpl3+, for example.
Some other files have different license statements. There is a subdirectory
popt containing a different COPYING (looks like X11 license).
The file snprintf.c in the subdirectory lib has:
/*
* Copyright Patrick Powell 1995
* This code is based on code written by Patrick Powell
(papowell@astart.com)
* It may be used for any purpose as long as this notice remains intact
* on all source code distributions
*/
There may potentially be as many licenses as files in the distribution
(208), that is why I went with only the main statement from the README
file.
What would good practice be?
Andreas
[-- Attachment #2: Type: text/html, Size: 8055 bytes --]
next prev parent reply other threads:[~2012-12-21 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 10:47 [PATCH] distro: Add rsync Andreas Enge
2012-12-21 12:28 ` Nikita Karetnikov
2012-12-21 13:17 ` Andreas Enge [this message]
2012-12-21 16:54 ` Ludovic Courtès
2012-12-21 19:13 ` Andreas Enge
2012-12-21 21:40 ` Ludovic Courtès
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=201212211417.58622.andreas@enge.fr \
--to=andreas@enge.fr \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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).