From: Gaius Mulley <gaius.mulley@southwales.ac.uk>
To: Florian Weimer <fweimer@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: state of play/strategy for including Modula-2 into the trunk (licence queries)
Date: Tue, 01 Oct 2019 12:28:00 -0000 [thread overview]
Message-ID: <87imp8ejle.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <87blv0vggz.fsf@oldenburg2.str.redhat.com> (Florian Weimer's message of "Tue, 1 Oct 2019 13:43:24 +0200")
Florian Weimer <fweimer@redhat.com> writes:
> * Gaius Mulley:
>
>> gm2 does use GNU libpth (to create context and switch contexts).
>> Although it doesn't need libpth for single process programs. I think
>> the GNU libpth project is no longer maintained, so I've included it in:
>>
>> http://git.savannah.gnu.org/cgit/gm2.git/tree/gcc-versionno/libgm2/libpth/pth
>
> libpth is dead upstream, I think, so it's not an ideal choice.
>
>> I assuming this is okay as it is an official GNU project? It contains
>> the important clause:
>>
>>> This library is free software; you can redistribute it and/or
>>> modify it under the terms of the GNU Lesser General Public
>>> License as published by the Free Software Foundation; either
>>> version 2.1 of the License, or (at your option) any later version.
>>
>> in its source files - so I plan to bump this to GPL3 with runtime
>> exception. Is this sensible and what is expected?
>
> Copyright has not been assigned to the FSF, so I wouldn't recommend
> making this change without consulting the major copyright holders
> first.
ah thanks - really useful info, I hadn't realised the copyright was not
assigned to the FSF.
> The question is whether this is really necessary. Obviously, there is
> no requirement to ship all supporting code under the GPL version 3 or
> later for GCC. See the libffi subdirectory, which has its own
> license.
sure I think it is looking sensible to stop using libpth. gm2 only
needs the two basic primitives create a context and switch to a context
in any case. Furthermore it only needs these if the user wants
coroutines. For most Modula-2 programs it isn't required.
> (Note: I'm just a random bystander here, this is not official policy.)
the feedback is really helpful - thanks,
regards,
Gaius
next prev parent reply other threads:[~2019-10-01 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 16:46 Gaius Mulley
2019-10-01 11:43 ` Florian Weimer
2019-10-01 12:28 ` Gaius Mulley [this message]
2019-10-01 12:40 ` Florian Weimer
2019-10-01 13:05 ` Gaius Mulley
2019-10-01 13:46 ` Matthias Klose
2019-10-01 19:01 ` Gaius Mulley
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=87imp8ejle.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius.mulley@southwales.ac.uk \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.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.
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).