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:01:08 +0200	[thread overview]
Message-ID: <20150722210108.GB3777@free.fr> (raw)
In-Reply-To: <20150721215438.19389da8@free-electrons.com>

Thomas, Luca, All,

On 2015-07-21 21:54 +0200, Thomas Petazzoni spake thusly:
> On Tue, 21 Jul 2015 18:29:44 +0200, Luca Ceresoli wrote:
> > There is no proper license file in the SNMP++ tarballs, so let's
> > extract it from a source file instead of copying it entirely.
> > 
> > Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> > ---
> >  package/snmppp/snmppp.mk | 8 +++++++-
> >  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> In many other packages we are using a complete source file as the
> license text. Should we switch to the solution you're proposing instead?
> Another possibility is to do:
> 
> <pkg>_LICENSE_FILES = src/v3.cpp:1:50
> 
> To tell the package infra to extract the text from lines 1 to 50. But
> we would never notice when the lines no longer match.
> 
> I'd like to have a general agreement on this before going further with
> your patch.

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.

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:01 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 [this message]
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
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=20150722210108.GB3777@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