From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Philip McGrath" <philip@philipmcgrath.com>,
"Maxime Devos" <maximedevos@telenet.be>, <55998@debbugs.gnu.org>
Subject: [bug#55998] [PATCH] gnu: Add cctools.
Date: Wed, 15 Jun 2022 22:20:34 +0100 [thread overview]
Message-ID: <CKR0TCX37H8E.3F7YYLX34VEDI@guix-aspire> (raw)
In-Reply-To: <0de6f5e5-c58b-354f-3ee0-18e824b7779a@philipmcgrath.com>
On Wed Jun 15, 2022 at 10:00 PM BST, Philip McGrath wrote:
> According to
> <https://www.gnu.org/philosophy/free-sw.html#legal-details>, "It is
> acceptable for a free license to specify which jurisdiction's law
> applies, or where litigation must be done, or both."
Although I don't know anything about licensing, wouldn't this mean a
company could, for example, publish software under a license that states
that disputes must be resolved in some theoretical country that bans all
free sharing of software (even if the owner wants to share it), then sue
somebody who's modified the ostensibly free software for copyright
infringement, winning because the country forbids any software sharing,
and still have the license count as free?
I'm probably misunderstanding this; surely there wouldn't be such a
gaping hole in the FSF's free license definition?
next prev parent reply other threads:[~2022-06-15 21:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 17:15 [bug#55998] [PATCH] gnu: Add cctools Philip McGrath
2022-06-15 18:32 ` Maxime Devos
2022-06-15 18:45 ` Maxime Devos
2022-06-15 19:06 ` Philip McGrath
2022-06-15 19:35 ` Maxime Devos
2022-06-15 21:00 ` Philip McGrath
2022-06-15 21:11 ` Maxime Devos
2022-06-15 21:20 ` ( via Guix-patches via [this message]
2022-06-15 18:53 ` Maxime Devos
2022-06-15 19:19 ` Philip McGrath
2022-06-15 20:07 ` Maxime Devos
2022-06-17 11:28 ` Philip McGrath
2022-06-15 18:55 ` Maxime Devos
2022-06-15 19:34 ` Philip McGrath
2022-06-15 18:56 ` Maxime Devos
2022-06-15 19:21 ` Philip McGrath
2022-06-15 19:23 ` Maxime Devos
2022-06-17 11:19 ` Philip McGrath
2022-06-15 20:04 ` Maxime Devos
2022-06-17 11:09 ` Philip McGrath
2022-06-19 21:01 ` Ludovic Courtès
2022-06-15 20:17 ` Maxime Devos
2022-06-16 22:29 ` Philip McGrath
2022-06-17 6:14 ` Maxime Devos
2022-06-15 20:18 ` Maxime Devos
2022-06-15 20:23 ` Maxime Devos
2022-06-16 23:29 ` Philip McGrath
2022-06-17 11:51 ` [bug#55998] [PATCH v2] " Philip McGrath
2022-06-19 21:02 ` bug#55998: [PATCH] " 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=CKR0TCX37H8E.3F7YYLX34VEDI@guix-aspire \
--to=guix-patches@gnu.org \
--cc=55998@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=paren@disroot.org \
--cc=philip@philipmcgrath.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).