From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Martin Jansa : gnu-config: update also bindir change to replace /usr/bin/ env instead of /usr/bin/perl
Date: Fri, 4 Feb 2011 17:05:48 +0100 [thread overview]
Message-ID: <20110204160548.GI3265@jama> (raw)
In-Reply-To: <AANLkTim=14HWLtuNDr5vqZSbt=o=MzF5QqVYGUOb_sKy@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On Fri, Feb 04, 2011 at 03:57:37PM +0000, Otavio Salvador wrote:
> On Fri, Feb 4, 2011 at 15:30, Tom Rini <tom_rini@mentor.com> wrote:
> > On 02/04/2011 08:11 AM, git version control wrote:
> ...
> >> gnu-config: update also bindir change to replace /usr/bin/env instead of
> >> /usr/bin/perl
> ...
> > This is wrong. /usr/bin/env is one of those mandated things everyone has.
> > And ${bindir} can be too long :) Based on the previous commit, this
> > test/regex should be able to go away.
>
> This is right since micro can build without /usr et all.
yes and ${bindir} is not that long :), only /usr/bin or like Otavio said
/bin ie for micro. That's why I fixed regexp instead of removing it.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-02-04 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1PlNJv-0005sP-PU@melo.openembedded.org>
2011-02-04 15:30 ` [oe-commits] Martin Jansa : gnu-config: update also bindir change to replace /usr/bin/ env instead of /usr/bin/perl Tom Rini
2011-02-04 15:57 ` Otavio Salvador
2011-02-04 16:05 ` Martin Jansa [this message]
2011-02-04 16:18 ` Tom Rini
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=20110204160548.GI3265@jama \
--to=martin.jansa@gmail.com \
--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 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.