public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bo Persson <bo@bo-persson.se>
To: libstdc++@gcc.gnu.org
Subject: Re: libstdc++ still has license conditions of SGI STL on top of GNU GPLv3+GCC Runtime Exception, right?
Date: Tue, 26 May 2020 11:03:18 +0200	[thread overview]
Message-ID: <8ff8f178-02b8-8776-204d-729c366e8be7@bo-persson.se> (raw)
In-Reply-To: <CAH6eHdQLy6_FWqKAPvgYjQe1_BmVER4QTSP+f5egbXFk+oPPpw@mail.gmail.com>

On 2020-05-26 at 10:27, Jonathan Wakely via Libstdc++ wrote:
> On Sun, 24 May 2020 at 02:09, P. - <pressbuttonsharder@gmail.com> wrote:
>>
>> There are a few ways where ignoring those licenses is possible:
>> 1) Hewlett-Packard and Silicon Graphics Computer Systems, Inc. has voluntarily contributed their code to be distributed under GCC's license and the notices are there for historical reason - can't find anything about that;
>> 2) FSF/libstdc++ maintainers has obtained special permissions from Hewlett-Packard and Silicon Graphics Computer Systems, Inc. to distribute their code under GCC's license - again, can't find anything;
>> 3) The license actually covers only notes and comments that exist only in header files - the libstdc++'s FAQ contradicts that (see the link in the original email);
>> 4) The code that is covered by those licenses exists only in compile time and is thrown away when compiled.
>>
>> The lawyer can't answer those 4 questions - only the libstdc++ maintainers/authors can.
> Those aren't question, they're statements, and I don't even know what
> the fourth one means. But anyway, my personal understanding is that
> none of them is true. It seems silly to assume that the licence terms
> stated in the file are only there accidentally, or some other
> convoluted assumption that contradicts the actual text in the files. A
> much simpler explanation is that you've misinterpreted the license
> terms. Talk to a lawyer if you're concerned.
>

Another prespective for P.:

Suppose Hewlett-Packard were to defend their copyright. They would then 
have so sue just about every software developer in the world. Who would 
then buy their products?!

My guess (I am not a lawyer :-) is that they are not that stupid.


    Bo Persson





  reply	other threads:[~2020-05-26  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 19:30 P. -
2020-05-23 22:13 ` Jonathan Wakely
2020-05-24  1:08   ` P. -
2020-05-26  8:27     ` Jonathan Wakely
2020-05-26  9:03       ` Bo Persson [this message]
2020-05-26 17:00       ` P. -
2020-05-26 17:18         ` Jonathan Wakely

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=8ff8f178-02b8-8776-204d-729c366e8be7@bo-persson.se \
    --to=bo@bo-persson.se \
    --cc=libstdc++@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).