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] snmppp: extract license text from source files
Date: Wed, 22 Jul 2015 23:26:13 +0200	[thread overview]
Message-ID: <20150722232613.149d5890@free-electrons.com> (raw)
In-Reply-To: <20150722210108.GB3777@free.fr>

Yann, Luca,

On Wed, 22 Jul 2015 23:01:08 +0200, Yann E. MORIN wrote:

> My point of view in the case there is no license file in the package:
> 
>  1) we should not regenerate a file, neither manually nor automatically:
>     - the automatic part (i.e. in the infra) can be easily foiled when a
>       package is updated,
>     - the manual part (like suggested by Luca) can also, but to a lower
>       extent, be broken on updates;
> 
>  2) if we refer to a file, it should be an existing file like a source
>     file.
> 
> But all-in-all, I believe we should not refer to a license file if
> there's none in the package.

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.

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

  reply	other threads:[~2015-07-22 21:26 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 [this message]
2015-07-22 21:33       ` Yann E. MORIN
2015-07-22 21:37         ` Thomas Petazzoni
2015-07-22 21:47           ` Yann E. MORIN
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=20150722232613.149d5890@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