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 v4] package/exiv2: cleanup options and licenses
Date: Thu, 6 Jun 2019 19:45:12 +0200	[thread overview]
Message-ID: <20190606174512.GA13603@scaer> (raw)
In-Reply-To: <20190606151549.GA2560@scaer>

All,,

On 2019-06-06 17:15 +0200, Yann E. MORIN spake thusly:
[--SNIP--]
> [...] Instead, we should have done
> something like:
>     package/exiv2/exiv2.mk:
>     ifeq ($(BR2_PACKAGE_EXIV2_LENSDATA),y)
>     EXIV2_LICENSE := $(EXIV2_LICENSE), Proprietary/Unknown (Nikon lens database)
>     endif

Scratch that part about the lens data; I read the current consdition
backwards...

Even then, it does not change the rest of the reasoning.

Regards,
Yann E. MORIN.

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

  reply	other threads:[~2019-06-06 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 13:51 [Buildroot] [PATCH v4] package/exiv2: cleanup options and licenses Nicolas Serafini
2019-06-05 21:45 ` Peter Seiderer
2019-06-06 13:02   ` Arnout Vandecappelle
2019-06-06 15:15     ` Yann E. MORIN
2019-06-06 17:45       ` Yann E. MORIN [this message]
2019-06-06 18:48       ` Arnout Vandecappelle
2019-06-06 18:55         ` Yann E. MORIN
2019-06-06 15:21     ` Nicolas Serafini
2019-06-08 16:35 ` Arnout Vandecappelle

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=20190606174512.GA13603@scaer \
    --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