From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Glenn Sommer <glemsom@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use full path to dnsdomainname and domainname in scripts/mkcompile_h
Date: Wed, 27 Jan 2010 10:44:29 +0800 [thread overview]
Message-ID: <2375c9f91001261844q474b05a2k6d96237fc925b706@mail.gmail.com> (raw)
In-Reply-To: <d65b1b151001261110j6c0561a1ifba2da0077698e54@mail.gmail.com>
On Wed, Jan 27, 2010 at 3:10 AM, Glenn Sommer <glemsom@gmail.com> wrote:
> 2010/1/26 Michal Marek <mmarek@suse.cz>:
>> On 26.1.2010 04:55, Américo Wang wrote:
>>> On Wed, Jan 20, 2010 at 11:06 PM, Glenn Sommer <glemsom@gmail.com> wrote:
>>>> Alternatively, if we want it to be more flexible(and allow the above)
>>>> - we should do something like:
>>>>
>>>> domainname_executable=`which domainname`
>>>> if [ ! -z "$domainname_executable" ] && [ -x "$domainname_executable" ]; then
>>>>
>>
>> (or 'if command -v domainname >/dev/null 2>&1; then domainname ...')
>>
>>
>>> Yeah, this seems better for me.
>>
>> Me too. Glenn, could you send a complete patch doing this? I'll add it
>> to the kbuild tree then.
>>
>> Thanks,
>> Michal
>>
>
> Yeah, good idea with "command -v" ! :)
> ( note: `command -v` will return true if the executable is found -
> else it will return false. )
>
> mkcompile_h is changed slightly in 2.6.32. Here's my new proposed patch:
>
>
> --- scripts/mkcompile_h.orig 2010-01-26 18:59:37.000000000 +0100
> +++ scripts/mkcompile_h 2010-01-26 20:03:42.000000000 +0100
> @@ -67,9 +67,9 @@
> echo \#define LINUX_COMPILE_BY \"`whoami`\"
> echo \#define LINUX_COMPILE_HOST \"`hostname | $UTS_TRUNCATE`\"
>
> - if [ -x /bin/dnsdomainname ]; then
> + if [ `command -v dnsdomainname 2> /dev/null` ]; then
> domain=`dnsdomainname 2> /dev/null`
> - elif [ -x /bin/domainname ]; then
> + elif [ `command -v domainname 2> /dev/null` ]; then
> domain=`domainname 2> /dev/null`
> fi
>
No, this doesn't look good.
First, you don't need to redirect stderr for 'command'.
Second, 'command' also searches in shell built-in commands, aliases,
so I prefer 'whereis -b'.
next prev parent reply other threads:[~2010-01-27 2:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 18:29 Glenn Sommer
2010-01-20 3:26 ` Américo Wang
2010-01-20 15:06 ` Glenn Sommer
2010-01-26 3:55 ` Américo Wang
2010-01-26 15:03 ` Michal Marek
2010-01-26 19:10 ` Glenn Sommer
2010-01-27 2:44 ` Américo Wang [this message]
2010-01-27 8:52 ` Michal Marek
2010-01-27 9:34 ` Américo Wang
[not found] ` <d65b1b151001270212q737706f1md00953155135b271@mail.gmail.com>
2010-01-27 10:14 ` Glenn Sommer
2010-01-27 13:15 ` Michal Marek
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=2375c9f91001261844q474b05a2k6d96237fc925b706@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=glemsom@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®