All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libkrb5: Bumb to 1.17
Date: Tue, 1 Oct 2019 17:44:49 +0200	[thread overview]
Message-ID: <20191001174449.57444ee1@windsurf.home> (raw)
In-Reply-To: <07349c8a-b244-5039-78a9-83b3e73e74f1@mind.be>

On Tue, 1 Oct 2019 17:41:36 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

> > But how exactly did you conclude those bits are irrelevant or wrong?
> > That's an issue I think, that we inject our own interpretation of the
> > licenses list and conclude of a resulting state.  
> 
>  Because it's what we do for all other packages? All autotools packages have a
> GPL config.guess script, but we never mention it. For many packages we don't
> include documentation because it doesn't get built/installed. Etc.
> 
>  If we don't want to do that, we should remove _LICENSE entirely.

Yes, I agree we should do something reasonable. Striving for perfection
in this area is basically impossible.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-01 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 11:39 [Buildroot] [PATCH] package/libkrb5: Bumb to 1.17 André Hentschel
2019-09-30 20:18 ` Thomas Petazzoni
2019-09-30 20:28   ` Yann E. MORIN
2019-09-30 22:13     ` Arnout Vandecappelle
2019-10-01 15:33       ` Yann E. MORIN
2019-10-01 15:41         ` Arnout Vandecappelle
2019-10-01 15:44           ` Thomas Petazzoni [this message]
2019-10-01 17:45           ` Yann E. MORIN

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=20191001174449.57444ee1@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 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.