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 17:59:05 +0000 [thread overview]
Message-ID: <1295978346.21832.3.camel@scimitar> (raw)
In-Reply-To: <3E839C39-204D-41DE-A334-E10C2761F807@dominion.thruhere.net>
On Tue, 2011-01-25 at 18:52 +0100, Koen Kooi wrote:
> Op 25 jan 2011, om 13:35 heeft Joshua Lock het volgende geschreven:
>
> > Hi all,
> >
> > When creating/editing recipes can we please ensure consistent use of
> > layout variables, rather than absolute paths.
> >
> > 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).
>
> Some care needs to be taking with that, though, since things like
> initscripts, config files and udev rules might have the hardcoded paths
> inside. In OE the 'micro' distro sets $prefix to "" instead of "/usr",
> which uncovered a world of hurt. Adding a sed s:usr/bin:${bindir}:g -i
> initscript to do_install is an easy enough way to fix it :)
>
Indeed, we have a few instances of that (particularly in meta-demo) -
good shout on something to keep an eye out for.
Thanks,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-01-25 17:59 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
2011-01-25 17:19 ` Saul Wold
2011-01-25 17:52 ` Koen Kooi
2011-01-25 17:59 ` Joshua Lock [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=1295978346.21832.3.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.