Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] ttf-inconsolata: fix license name
Date: Tue, 23 Apr 2013 12:09:45 +0200	[thread overview]
Message-ID: <20130423100945.GC3217@jama> (raw)
In-Reply-To: <CANyK_8cMTd4aTzAhHX8V3Zrs6pjZoctEfVr8hLNYJXo1WQUzFw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

On Tue, Apr 23, 2013 at 10:00:55AM +0100, Paul Barker wrote:
> On 23 April 2013 09:55, Paul Barker <paul@paulbarker.me.uk> wrote:
> > We have "SIL Open Font License" 1.1 in common-licenses as OFL-1.1.
> >
> 
> There's also a copy of the OFL 1.1 in
> meta-oe/recipes-graphics/ttf-fonts/ttf-inconsolata/OFL.txt as the
> bitbake recipe just downloads a single font file. I don't know how to
> do this as it goes across layers (not sure if relative paths would
> work) but would it be better to replace this with reference to the
> file in common-licenses? I realise this is there to satisfy having
> something in LIC_FILES_CHKSUM but it isn't doing the intended job as
> upstream could update the license and it wouldn't break this checksum.

You can use
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/OFL-1.1;md5=hash"

it's true, that this does not catch license change in upstream source,
but if there isn't any information about license in SRC_URI, then having
OFL.txt is as bad as ${COMMON_LICENSE_DIR}/OFL-1.1 reference imho.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-04-23 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23  8:55 [meta-oe][PATCH] ttf-inconsolata: fix license name Paul Barker
2013-04-23  9:00 ` Paul Barker
2013-04-23 10:09   ` Martin Jansa [this message]

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=20130423100945.GC3217@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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