Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] snmppp: extract license text from source files
Date: Wed, 22 Jul 2015 23:47:56 +0200	[thread overview]
Message-ID: <20150722214756.GD3777@free.fr> (raw)
In-Reply-To: <20150722233730.4b9fc845@free-electrons.com>

Thomas, All,

On 2015-07-22 23:37 +0200, Thomas Petazzoni spake thusly:
> On Wed, 22 Jul 2015 23:33:15 +0200, Yann E. MORIN wrote:
> > > The v3.cpp file is only 428 lines long, and weights 10260 bytes.
> > > Comparatively, the GPLv2 text is 339 lines long for 18092 bytes, and
> > > the GPLv3 text is 647 lines lon for 35147 bytes.
> > > 
> > > If you're really concerned about the file size used for the license of
> > > snmppp, we could switch to use src/gauge.cpp instead of src/v3.cpp.
> > > gauge.cpp is only 75 lines long, for 2804 bytes, and I'd say two thirds
> > > of the file contents are license stuff.
> > 
> > It's not about the size of the file. It's just that I find it odd to use
> > a source file as a license file.
> 
> If there's nothing better, then using a source file that carries a text
> of the license is good enough to act as a license file, IMO.

In principle, yes. However, consider this case:

  - package is BSD-3c licensed, so redistributing the source is not
    mandatory,

  - the user has a local patch for that package,

  - the user does not want to share those modifications, which he is
    allowed to do as per the BSD-3c,

  - using a source file as license file would "leak" those modifications
    (or part of those) in the legal-info.

So, using a source file is not perfect either.

(Note: I would prefer to live in an ideal world where "Open Source" did
not exist and only "Free-as-in-free-speach Software" did, but that's not
the world I'm living in, so... ;-) )

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-07-22 21:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 16:29 [Buildroot] [PATCH] snmppp: extract license text from source files Luca Ceresoli
2015-07-21 19:54 ` Thomas Petazzoni
2015-07-22 21:01   ` Yann E. MORIN
2015-07-22 21:26     ` Thomas Petazzoni
2015-07-22 21:33       ` Yann E. MORIN
2015-07-22 21:37         ` Thomas Petazzoni
2015-07-22 21:47           ` Yann E. MORIN [this message]
2015-07-22 21:50             ` Thomas Petazzoni

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=20150722214756.GD3777@free.fr \
    --to=yann.morin.1998@free.fr \
    --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