From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/8] fontconfig: add license info
Date: Wed, 22 Aug 2012 09:46:32 +0300 [thread overview]
Message-ID: <20120822064631.GF3829@tarshish> (raw)
In-Reply-To: <CANxTyt7w48eF1TBWJzbtaz_uao988-=y6W6LhTJF+CP9FUJNCg@mail.gmail.com>
Hi Danomi,
On Tue, Aug 21, 2012 at 08:39:26PM -0400, Danomi Manchego wrote:
> > For special licenses, I thought that the convention was to use the
> > string "foo license", and not just "foo".
>
> Grepping, I see only three exceptions to this:
>
> package/zxing/zxing.mk:ZXING_LICENSE = Apache
> package/poco/poco.mk:POCO_LICENSE = Boost-v1.0
Apache and Boost refer (also) to specific software licenses. See
http://www.apache.org/licenses/ and http://www.boost.org/users/license.html. I
think we should add a version number to Apache license info, though. In the
case of zxing it's v2.0.
baruch
> package/openssl/openssl.mk:OPENSSL_LICENSE = OpenSSL or SSLeay
>
> So, I'll resubmit as "fontconfig license".
>
> What about sqlite? According to http://www.sqlite.org/copyright.html, it
> is "public domain". Should sqlite's license also be "sqlite license", or
> "public domain"?
>
> Danomi -
> On Tue, Aug 21, 2012 at 6:56 AM, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
>
> > Le Sun, 19 Aug 2012 16:18:28 -0400,
> > Danomi Manchego <danomimanchego123@gmail.com> a ?crit :
> >
> > > +FONTCONFIG_LICENSE = fontconfig
> > > +FONTCONFIG_LICENSE_FILES = COPYING
> >
> > For special licenses, I thought that the convention was to use the
> > string "foo license", and not just "foo". Luca?
> >
> > Thomas
> > --
> > Thomas Petazzoni, Free Electrons
> > Kernel, drivers, real-time and embedded Linux
> > development, consulting, training and support.
> > http://free-electrons.com
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-08-22 6:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 20:18 [Buildroot] [PATCH 1/8] alsa-lib: add license info Danomi Manchego
2012-08-19 20:18 ` [Buildroot] [PATCH 2/8] alsa-utils: " Danomi Manchego
2012-08-19 20:18 ` [Buildroot] [PATCH 3/8] faad2: " Danomi Manchego
2012-08-19 20:18 ` [Buildroot] [PATCH 4/8] nano: " Danomi Manchego
2012-08-19 20:18 ` [Buildroot] [PATCH 5/8] fbdump: " Danomi Manchego
2012-08-19 20:18 ` [Buildroot] [PATCH 6/8] fontconfig: " Danomi Manchego
2012-08-21 10:56 ` Thomas Petazzoni
2012-08-22 0:39 ` Danomi Manchego
2012-08-22 6:46 ` Baruch Siach [this message]
2012-08-26 21:40 ` Arnout Vandecappelle
2012-08-27 9:42 ` Luca Ceresoli
2012-08-19 20:18 ` [Buildroot] [PATCH 7/8] rsync: " Danomi Manchego
2012-08-19 20:18 ` [Buildroot] [PATCH 8/8] librsync: " Danomi Manchego
2012-08-21 11:00 ` [Buildroot] [PATCH 1/8] alsa-lib: " 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=20120822064631.GF3829@tarshish \
--to=baruch@tkos.co.il \
--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