From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 4/4] Renamed prefix_native, bindir_native, etc using hyphens
Date: Thu, 18 Mar 2010 21:13:42 +0000 [thread overview]
Message-ID: <1268946822.8697.71.camel@rex> (raw)
In-Reply-To: <4BA291BB.7040106@tait.co.nz>
On Fri, 2010-03-19 at 09:48 +1300, Douglas Royds wrote:
> Any renaming of base_prefix, exec_prefix, base_bindir, target_datadir,
> &c is a separate matter. Note that some of these names are imposed on us
> by Autotools convention. This is why these variables are in lower case
> in the first place:
>
> http://www.gnu.org/prep/standards/html_node/Directory-Variables.html#Directory-Variables
Exactly, this is why they are as they are and I don't think changing
this is practical.
It would in fact be more feasible to switch to a "new" character for
overrides in bitbake...
Cheers,
Richard
prev parent reply other threads:[~2010-03-18 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 4:56 [PATCH 4/4] Renamed prefix_native, bindir_native, etc using hyphens Douglas Royds
2010-03-18 7:18 ` Frans Meulenbroeks
2010-03-18 10:38 ` Phil Blundell
2010-03-18 20:48 ` Douglas Royds
2010-03-18 21:13 ` Richard Purdie [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=1268946822.8697.71.camel@rex \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox