All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Winship <danw@gnome.org>
To: "Burton, Ross" <ross.burton@intel.com>, Sander Visser <sander@visser.se>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: libsoup license
Date: Fri, 18 Sep 2015 16:43:21 -0400	[thread overview]
Message-ID: <55FC7769.8030307@gnome.org> (raw)
In-Reply-To: <CAJTo0LZY5kfRN3Ed1tBicPSX3yZOYExcO=U6eiccv2AkO4pE+g@mail.gmail.com>

On 09/18/2015 04:07 PM, Burton, Ross wrote:
> To be honest libsoup isn't very clear
...
> Dan: exactly what license is libsoup under?  LGPL v2 precisely, or LGPL
> v2 or greater?

I don't know either. :-)

It was initially written at a time when Ximian was explicitly using the 
"v2 only" license on evolution (because reasons), so it's possible that 
libsoup was intended to be v2 only, since it was more-or-less part of 
evolution. But then, Novell relicensed evolution to v2+ later on, so 
presumably, if libsoup actually was v2-only at that point (which it may 
not have been), then surely Novell *intended* to also make libsoup v2+, 
despite not having said so. So... "maybe it used to be v2+" + "probably 
it was intended to have been changed to v2+ later if it wasn't already" 
+ "certainly everything written since 2007 was intended to be v2+" == 
"probably definitely it's v2+ now" ? That's totally how the law works, 
right?

-- Dan



  reply	other threads:[~2015-09-18 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 10:32 libsoup license Sander Visser
2015-09-18 20:07 ` Burton, Ross
2015-09-18 20:43   ` Dan Winship [this message]
2015-09-18 21:32     ` Burton, Ross

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=55FC7769.8030307@gnome.org \
    --to=danw@gnome.org \
    --cc=ross.burton@intel.com \
    --cc=sander@visser.se \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.