public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc@gcc.gnu.org
Subject: Re: Libiberty license roundup (questions/potential problems)
Date: Sat, 24 May 2003 07:08:00 -0000	[thread overview]
Message-ID: <20030524045830.GA1370@doctormoo> (raw)

I wrote a longer message about this, but then lost it.  :-)

The following is a problem.  Some files say "This file is part of the 
libiberty library.  This library... under the terms of the GNU General 
Public License..."

Others say "This file is part of the libiberty library.  Libiberty... 
under the terms of the GNU Library General Public License..."

If "this library" is read to mean "the libiberty library", then one file 
says "libiberty can be used under the LGPL", while a GPLed file says 
"I'm part of libiberty".  This isn't so good.

I therefore suggest the "This file" or "This program" form of 
boilerplate for all files in libiberty to make the separate licenses quite
clear and distinct.  The line "This file is part of the libiberty 
library" is fine, provided the rest of the lines state 
specifically that they apply only to 'this file', not to the whole of 
'the libiberty library'.

Alternatively, "libiberty" could be properly restricted to files with a 
certain licence (or licenses which can be 'converted' to that one); 
those files could say "Libiberty is..." while the others (pure GPL, 
for instance) would say "This file is..." or  "This file is part of GCC.  
GCC is..." or some such.  But that's more confusing.  :-)

--Nathanael

             reply	other threads:[~2003-05-24  4:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24  7:08 Nathanael Nerode [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-29  0:10 Robert Dewar
2003-05-28 22:50 Robert Dewar
2003-05-28 23:58 ` Joe Buck
2003-05-24 14:59 Robert Dewar
2003-05-24  4:07 Nathanael Nerode
2003-05-24 14:07 ` DJ Delorie
2003-05-23 23:06 Nathanael Nerode
2003-05-23 23:16 ` DJ Delorie
2003-05-24  1:23 ` Mike Stump
2003-05-24  1:32   ` Andrew Cagney
2003-05-24  1:37     ` DJ Delorie
2003-05-28 21:10       ` Andrew Cagney
2003-05-28 22:25         ` Joe Buck
2003-05-30 17:37 ` David O'Brien
2003-05-30 19:05   ` DJ Delorie

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=20030524045830.GA1370@doctormoo \
    --to=neroden@twcny.rr.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).