unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Danckaert <post@thomasdanckaert.be>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 26312@debbugs.gnu.org
Subject: bug#26312: [PATCH] gnu: Add cifs-utils.
Date: Sun, 02 Apr 2017 12:52:49 +0200	[thread overview]
Message-ID: <cuc37drw072.fsf@thomasdanckaert.be> (raw)
In-Reply-To: <87lgrkavxy.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Sat, 01 Apr 2017 19:18:01 +0200")

Marius Bakke <mbakke@fastmail.com> writes:

> Could you mention which files, since it's only three? I also think
> listing both lgpl2.1+ and lgpl3+ is redundant; if these source files
> interact in some way the result is effectively lgpl3+. If the LGPL2.1+
> code is what is installed, I would pick that since it implies LGPL3+.

The files are source/util.{h,c} (lgpl2.1+), and source/cifs_spnego.h
(lgpl3+), I'll add that in a comment.

About the lgpl2.1+ vs lgpl3+ thing, I'm a bit confused about what we
actually want to communicate with the license field (and probably about
license issues in general).  As far as I know, all code (lgpl2.1+ and
lgpl3+ files) is installed (compiled).  Because the rest of the code is
GPL3+, I think a linked binary (e.g. a substitute from hydra) can only
be distributed as GPL3+?  In addition to that, there are 3 source files,
which can are individually licensed as LGPL2.1+ and LGPL3+, which why we
specify a list of licenses, I thought?  In that case I don't really
understand why mentioning only lgpl2.1+ would be sufficient (lgpl3+ is
more strict?).

I'm just trying to understand so I get this stuff right the next time...
Not counting the license itself, the lgpl3+ file is only 25 lines :-)

cheers,

Thomas

  reply	other threads:[~2017-04-02 10:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 15:48 bug#26312: [PATCH] gnu: Add cifs-utils Thomas Danckaert
2017-03-30 20:19 ` Tobias Geerinckx-Rice
2017-04-01  6:47   ` Thomas Danckaert
2017-04-01 17:18     ` Marius Bakke
2017-04-02 10:52       ` Thomas Danckaert [this message]
2017-04-02 11:35         ` Marius Bakke
2017-04-02 16:14           ` Thomas Danckaert
2017-04-03 20:02           ` Thomas Danckaert

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=cuc37drw072.fsf@thomasdanckaert.be \
    --to=post@thomasdanckaert.be \
    --cc=26312@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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).