public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <burlingk@cv63.navy.mil>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] 2 to 3??
Date: Wed, 18 Jul 2007 20:07:04 +0900	[thread overview]
Message-ID: <14178ED3A898524FB036966D696494FB138F21@messenger.cv63.navy.mil> (raw)



> -----Original Message-----
> From: b.n. [mailto:brullonulla@gmail.com] 
> Sent: Wednesday, July 18, 2007 6:29 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] 2 to 3??
> 
> 
> Personally I'm quite happy with both GPLv2 and GPLv3. 
> Frankly, my only 
> real, serious concern is the fact that the two licences are 
> incompatible.
> 
> The fact compatibility has not explicitly allowed sounds 
> plain crazy to 
> me. 
>
> When I tried asking about how to have some degree of compatibility 
> between GPLv2 and GPLv3 in code I write, everyone told me 
> "just license it under GPLv2 or any later version". The problem 
> is that in this case I have to blindly trust the FSF about anything 
> that will come out of it. 
>

That honestly is the only real way to make them compatible,
to use the "or any later version" clause.

Version 3 only allows for very specific modifications to itself.
Version 2 was a little more forgiving.

Version 3 says "Here is a list of optional clauses."

There are other options, but they make it into a new license.
--
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2007-07-18 10:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 11:07 burlingk [this message]
2007-07-18 12:29 ` [gentoo-user] 2 to 3?? Dan Cowsill
  -- strict thread matches above, loose matches on Subject: below --
2007-07-19 14:37 burlingk
2007-07-19  6:13 burlingk
2007-07-19  5:59 ` Boyd Stephen Smith Jr.
2007-07-19  5:54 burlingk
2007-07-18  4:26 burlingk
2007-07-18  4:18 burlingk
2007-07-17 17:57 burlingk
2007-07-18 13:51 ` Stroller
2007-07-17 17:38 burlingk
2007-07-17 17:27 ` Boyd Stephen Smith Jr.
2007-07-18 12:38   ` Alan McKinnon
2007-07-18 14:13     ` Stroller
2007-07-18 16:15     ` Boyd Stephen Smith Jr.
2007-07-18 13:48 ` Stroller
2007-07-18 16:33   ` Boyd Stephen Smith Jr.
2007-07-17 12:12 burlingk
2007-07-17 11:29 ` Abraham Marín Pérez
2007-07-17 10:14 burlingk
2007-07-17 10:42 ` Abraham Marín Pérez
2007-07-17 11:01 ` Graham Murray
2007-07-17 12:48   ` Stroller
2007-07-17 16:19     ` Volker Armin Hemmann
2007-07-18 13:13       ` Stroller
2007-07-18 17:40         ` Volker Armin Hemmann
2007-07-18 18:10           ` Boyd Stephen Smith Jr.
2007-07-18 22:34           ` Stroller
2007-07-18 23:48             ` Volker Armin Hemmann
2007-07-19  0:41               ` Boyd Stephen Smith Jr.
2007-07-19  2:10                 ` Stroller
2007-07-19  1:58               ` Stroller
2007-07-17 17:14 ` Boyd Stephen Smith Jr.
2007-07-17 19:29   ` Mike Edenfield
2007-07-16  0:52 burlingk
2007-07-16 12:15 ` Mark Shields
2007-07-16 21:53   ` Jerry McBride
2007-07-17  1:26     ` Volker Armin Hemmann
2007-07-17  1:59       ` Boyd Stephen Smith Jr.
2007-07-17  1:26   ` Volker Armin Hemmann
2007-07-17  2:08     ` Henk Boom
2007-07-13 22:11 Jerry McBride
2007-07-13 22:27 ` Bo Ørsted Andresen
2007-07-18  9:28 ` b.n.
2007-07-18 16:23   ` Boyd Stephen Smith Jr.

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=14178ED3A898524FB036966D696494FB138F21@messenger.cv63.navy.mil \
    --to=burlingk@cv63.navy.mil \
    --cc=gentoo-user@lists.gentoo.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