all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: guix-devel <guix-devel@gnu.org>
Subject: Question about multiple licenses
Date: Sat, 26 Aug 2017 13:10:32 +0530	[thread overview]
Message-ID: <681c721c.AEQAPExWoDUAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZoSX-@mailjet.com> (raw)


I'm packaging linkchecker.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27468

Different files of linkchecker have different license headers. The
license field of the package is as follows:

(license (list l:gpl2+
               l:bsd-2 ; linkcheck/better_exchook2.py
               l:bsd-3 ; linkcheck/colorama.py
               l:psfl  ; linkcheck/gzip2.py
               l:expat ; linkcheck/mem.py
               l:isc   ; third_party/dnspython
               l:asl2.0))

gpl2+ is a stricter license than the other licenses, and covers the
"program as a whole". So, do we really need to mention the other
licenses, especially those licenses which cover only one source file? Is
it a good idea to hide the multiple licenses from the user, and just
mention gpl2+ as the license of the whole package?

             reply	other threads:[~2017-08-26  7:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-26  7:40 Arun Isaac [this message]
2017-08-28 10:45 ` Question about multiple licenses Alex Vong
2017-08-28 17:25   ` Arun Isaac
2017-08-28 17:29     ` Efraim Flashner
2017-08-29  6:30       ` Arun Isaac
2017-09-01 11:43   ` Dave Love
2017-09-02 16:54     ` Alex Vong
2017-09-07 16:21       ` Dave Love
2017-09-03 11:45     ` Arun Isaac
2017-09-04 14:57     ` Ludovic Courtès
2017-09-07 16:20       ` Dave Love
2017-09-10 20:54         ` Ludovic Courtès
2017-09-11 11:29           ` Alex Vong
2017-09-11 12:45             ` Andy Wingo
2017-09-12 22:15               ` Dave Love
2017-09-12 22:13           ` Dave Love

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=681c721c.AEQAPExWoDUAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZoSX-@mailjet.com \
    --to=arunisaac@systemreboot.net \
    --cc=guix-devel@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.