From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt: add font license information
Date: Tue, 23 Feb 2016 20:39:25 +0100 [thread overview]
Message-ID: <56CCB56D.2000802@mind.be> (raw)
In-Reply-To: <20160223135110.064721b6@free-electrons.com>
On 02/23/16 13:51, Thomas Petazzoni 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.
Actually, that last bit could be moved to the legal-info infra itself, e.g. in
the legal-manifest function.
But that's for another patch :-)
Regards,
Arnout
>
> Thomas
>
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-23 19:39 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 [this message]
2016-02-23 20:19 ` Peter Seiderer
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=56CCB56D.2000802@mind.be \
--to=arnout@mind.be \
--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