All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: License info now mandatory?
Date: Fri, 07 Jan 2011 06:54:43 -0700	[thread overview]
Message-ID: <4D271B23.8060107@mlbassoc.com> (raw)

I have a number of recipes (from various places, mostly OE)
that don't have explicit license information in them.  For now,
I'm happy just knowing this fact - these things can be cleaned
up eventually.  Until recently, there were warnings about this
but now, such recipes are considered fatal errors.  For example:

| ERROR: icu-native: Recipe file does not have license file information (LIC_FILES_CHKSUM)

I understand such strict policies for Poky & Yocto in general,
but not all may want to be so pedantic over this topic.

Is there some way to temper this, e.g. go back to warnings?

n.b. I'm fully in favour of proper licensing, I'd just like
to be able to control how strongly I apply this policy.

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


                 reply	other threads:[~2011-01-07 13:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4D271B23.8060107@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.