Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/dovecot: New package
Date: Fri, 3 Oct 2014 13:40:24 +0200	[thread overview]
Message-ID: <20141003134024.4de4020b@free-electrons.com> (raw)
In-Reply-To: <XnsA3BB7588C35A8berndkuhlsPkbjNfxxIA@bernd-kuhls.de>

Dear Bernd Kuhls,

On Fri, 03 Oct 2014 11:33:15 +0200, Bernd Kuhls wrote:

> how to do that?
> Are the websites where I can upload license files for checking?
> 
> I compared http://www.gnu.org/licenses/lgpl-2.1.txt and 
> http://www.dovecot.org/doc/COPYING.LGPL, they are 100% identical.
> 
> http://www.dovecot.org/doc/COPYING says:
> "Everything else is LGPLv2.1 (see COPYING.LGPL) unless otherwise mentioned
> at the beginning of the file."

Regarding LGPLv2.1 vs. LGPLv2.1+ it's not written in the license text
(the license text is just one particular version), but in the header of
each source file, where you have a "(or later)" specification if it's
with "+", or no such specification when it's just one particular
version that applies.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-10-03 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28 17:25 [Buildroot] [PATCH 1/2] package/dovecot: New package Bernd Kuhls
2014-09-28 17:25 ` [Buildroot] [PATCH 2/2] package/dovecot-pigeonhole: " Bernd Kuhls
2014-09-29 17:14   ` Thomas Petazzoni
2014-09-29 17:13 ` [Buildroot] [PATCH 1/2] package/dovecot: " Thomas Petazzoni
2014-10-03  9:33   ` Bernd Kuhls
2014-10-03 11:40     ` Thomas Petazzoni [this message]
2014-10-03 12:32       ` Bernd Kuhls
2014-10-03 14:12   ` Bernd Kuhls

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=20141003134024.4de4020b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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