From: Darren Hart <dvhart@linux.intel.com>
To: Joshua Lock <josh@linux.intel.com>
Cc: poky <poky@yoctoproject.org>
Subject: Re: Please ensure you are using layout variables in recipes
Date: Tue, 25 Jan 2011 07:50:12 -0800 [thread overview]
Message-ID: <4D3EF134.3030803@linux.intel.com> (raw)
In-Reply-To: <1295958916.5641.8.camel@scimitar>
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?
--
Darren
>
> For example use:
>
> ${bindir}/foo
> ${datadir}/bar
> and
> ${base_sbindir}/baz
>
> rather than:
>
> /usr/bin/foo
> /usr/share/bar
> and
> /sbin/baz
>
> The layout variables are defined in bitbake.conf and we should have
> pretty much everything we need there, if you feel some are missing
> please submit a patch (we've recently added some for cross and nativesdk
> use, for example).
>
> Thanks,
> Joshua
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-01-25 15:50 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 [this message]
2011-01-25 16:00 ` Joshua Lock
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=4D3EF134.3030803@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=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.