Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt: add font license information
Date: Tue, 23 Feb 2016 21:19:46 +0100	[thread overview]
Message-ID: <20160223211946.08dbb7c6@gmx.net> (raw)
In-Reply-To: <20160223135110.064721b6@free-electrons.com>

Hello Thomas,

On Tue, 23 Feb 2016 13:51:10 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Arnout,
> 
> Thanks a lot for having reviewed this patch, which is not very simple
> in terms of licensing details.
> 
> On Tue, 23 Feb 2016 00:09:24 +0100, Arnout Vandecappelle wrote:
> 
> >  The problem with the way that it's done now is that the different licenses will
> > not be comma-separated while they usually are. But adding commas is difficult in
> > this case, so OK.
> 
> I thought we could do something such as:
> 
> QT_LICENSE += Foo (bar),
> QT_LICENSE += Bar (foo),
> QT_LICENSE += Baz (boz),
> QT_LICENSE := $(patsubst %$(comma),%,$(QT_LICENSE))
> 
> But it unfortunately seems to remove all commas. We could then do:
> 
> QT_FINAL_LICENSE = $(shell echo "$(QT_LICENSE)" | sed 's:\(.*\),:\1:')
> 
> Not super pretty, but it's just one line of crap.

O.k. will take it for the next patch version...

Regards,
Peter

> 
> Thomas

  parent reply	other threads:[~2016-02-23 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 20:22 [Buildroot] [PATCH v1] qt: add font license information Peter Seiderer
2016-02-22 23:09 ` Arnout Vandecappelle
2016-02-23 12:51   ` Thomas Petazzoni
2016-02-23 19:39     ` Arnout Vandecappelle
2016-02-23 20:19     ` Peter Seiderer [this message]
2016-02-23 20:02   ` Peter Seiderer

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=20160223211946.08dbb7c6@gmx.net \
    --to=ps.report@gmx.net \
    --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