From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: Please ensure you are using layout variables in recipes
Date: Tue, 25 Jan 2011 16:00:29 +0000 [thread overview]
Message-ID: <1295971229.21832.1.camel@scimitar> (raw)
In-Reply-To: <4D3EF134.3030803@linux.intel.com>
On Tue, 2011-01-25 at 07:50 -0800, Darren Hart wrote:
> On 01/25/2011 04:35 AM, Joshua Lock wrote:
> > Hi all,
> >
> > When creating/editing recipes can we please ensure consistent use of
> > layout variables, rather than absolute paths.
>
> Hi Josh,
>
> When I was putting together the mediatomb scripts I remember running
> into this. We typically have to write custom init scripts, for example,
> in order to deal with this as well as some other subtleties and
> assumptions made by the package init author. In these cases, it would be
> really useful to have a layer skeleton, which also included skeleton
> recipes, images, etc. All commented, complete with documentation links
> to aid people through the process. Seeing it all together in final form
> would go a long way to helping people get it right the first (or maybe
> the second) time. I've discussed this with Saul as well, maybe something
> we need to get on the schedule?
I was just proposing something similar. Of course all of our metadata
should meet the same high standards but it would make sense to have
somewhere to point at as the canonical example.
Scheduling time to work providing example definitely gets my backing.
Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-25 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 12:35 Please ensure you are using layout variables in recipes Joshua Lock
2011-01-25 15:50 ` Darren Hart
2011-01-25 16:00 ` Joshua Lock [this message]
2011-01-25 17:19 ` Saul Wold
2011-01-25 17:52 ` Koen Kooi
2011-01-25 17:59 ` Joshua Lock
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=1295971229.21832.1.camel@scimitar \
--to=josh@linux.intel.com \
--cc=poky@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.