From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
"peterengcomau001@adam.com.au" <peterengcomau001@adam.com.au>
Subject: Re: is it not a *requirement* that layers start with "meta-"?
Date: Mon, 5 Jan 2015 12:08:07 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1501051201210.23745@localhost> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237988E9070A@ORSMSX101.amr.corp.intel.com>
On Mon, 5 Jan 2015, Rifenbark, Scott M wrote:
> If anyone can locate some scripts or something that actually does
> require "meta-" to be prepended please let me know. That changes
> how we describe this.
as an admittedly simple example, i ran across this in oe-core's
scripts/contrib/documentation-audit.sh:
for pkg in `bitbake -s | awk '{ print \$1 }'`; do
... snip ...
if [[ "$pkg" =~ ^meta- || "$pkg" =~ ^packagegroup- || "$pkg" =~ -image ]]; then
# Skip meta, task and image recipes
continue
fi
checking that the package name starts with "meta-" seems to
pretty clearly suggest that it will be treated differently than if it
doesn't. i'm sure no one is terribly worried about that particular
script, but it does seem to show an example of this.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-01-05 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 14:20 is it not a *requirement* that layers start with "meta-"? Robert P. J. Day
2014-12-30 15:45 ` peterengcomau001
2014-12-30 19:24 ` Robert P. J. Day
2015-01-05 16:42 ` Rifenbark, Scott M
2015-01-05 17:08 ` Robert P. J. Day [this message]
2015-01-08 13:20 ` Anders Darander
2015-01-08 13:31 ` Robert P. J. Day
[not found] <mailman.26028.1420723936.26702.yocto@yoctoproject.org>
2015-01-08 14:05 ` micke.prag
2015-01-08 14:15 ` Robert P. J. Day
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=alpine.LFD.2.11.1501051201210.23745@localhost \
--to=rpjday@crashcourse.ca \
--cc=peterengcomau001@adam.com.au \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@yoctoproject.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.