From: Maxime Devos <maximedevos@telenet.be>
To: 宋文武 <iyzsong@envs.net>, guix-devel@gnu.org
Subject: Re: Clarify the license field of the package
Date: Fri, 26 Aug 2022 20:38:10 +0200 [thread overview]
Message-ID: <446d3577-8137-8346-a87b-6453c999eb1c@telenet.be> (raw)
In-Reply-To: <87a67wabwf.fsf@envs.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 2556 bytes --]
On 22-08-2022 11:02, 宋文武 wrote:
> Hello list, I have some questions about the 'license' of a package,
> currently defined as:
>
> The license of the package; a value from ‘(guix licenses)’, or a
> list of such values.
>
> 1. It's the license of source files (guix build -S) or built binary
> files?
(If 'built binary files', I would include generated or copied
documentation in the list. And icons, .desktop files, ..., I'm not
restricting myself to _executable_ binaries here and also not to
binaries that aren't sources as well.)
Rarely, there is some weirdness where the source code is free
(VSCodium?) but the official build has a non-free license (VSCode?). At
least for that example, it doesn't apply to Guix though (because
VSCodium is not packaged, and because with some rare exceptions we build
from source).
However, in my experience, in free software they almost always have the
same license, so the distinction appears meaningless to me with the
possible exception of build scripts and test files (including, but not
limited to, test code).
I think it should include the source files, as the license of the source
is important for people doing 'guix build --source'.
> 2. When its value is a list of multiple licenses, it's files under
> different licenses (eg: lib/*.so under LGPL, while bin/* under GPL),
> or files under one license select from choices?
>
> My guess is that the license field is for source files since we can
> disable binary substitutes, and list is used for files under different
> licenses.
>
> Does my guess is correct? Thank you!
As answered in a reply to a patch, myself I go for 'files under
different licenses' -- to me it seems hard to go wrong with 'just
include all participating licenses' instead of trying to make a selection.
However, keep in mind that sometimes a file is part licensed as, say,
BSD(*), part as Expat, with modifications under the GPL -- to me it
appears that for practical purposes you could consider such a thing to
be 'effectively GPL', but that's not 100% accurate, as it appears
required to preserve the BSD and Expat license text. (Such things can
happen when incorporating code from other, differently-licensed, projects).
(*) let's say without the advertising clause or whatever it was (IIRC
and IIUC the original BSD was incompatible with the GPL?).
If there's some consensus, I think it would be nice to clarify this
matter in the manual.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-26 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:02 Clarify the license field of the package 宋文武
2022-08-26 18:08 ` John Kehayias
2022-08-29 2:43 ` 宋文武
2022-08-26 18:38 ` Maxime Devos [this message]
2022-08-29 3:39 ` 宋文武
2022-09-01 13:12 ` Maxim Cournoyer
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=446d3577-8137-8346-a87b-6453c999eb1c@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=iyzsong@envs.net \
/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).