Andre Poenitz wrote:
> On Wed, May 25, 2005 at 11:56:19AM +0100, Angus Leeming wrote:
>> Angus Leeming wrote:
>> >Or maybe tr?
>> >
>> >test `uname -s | grep 'MINGW'` && {
>
>
> I wonder whether this might be equivalent to
>
>.. uname -s | grep -q MINGW * ...
Sigh. Of course you're ri
On Wed, May 25, 2005 at 11:56:19AM +0100, Angus Leeming wrote:
> Angus Leeming wrote:
> >Or maybe tr?
> >
> >test `uname -s | grep 'MINGW'` && {
I wonder whether this might be equivalent to
.. uname -s | grep -q MINGW * ...
Andre'
Jean-Marc Lasgouttes wrote:
Is it possible to use
if test ; then ... fi
instead of
test && { ... }
?
This is the style used in the rest of the script.
Sure. Done.
Angus
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
| Angus> Angus Leeming wrote:
>>> Or maybe tr? test `uname -s | grep 'MINGW'` && { # Before running
>>> chkconfig.sed, remove the trailing '\r' # characters that can
>>> bugger up various
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Angus Leeming wrote:
>> Or maybe tr? test `uname -s | grep 'MINGW'` && { # Before running
>> chkconfig.sed, remove the trailing '\r' # characters that can
>> bugger up various versions of sed. tr -d '\r' < chkconfig.sed >
>> chkconf
Angus Leeming wrote:
Or maybe tr?
test `uname -s | grep 'MINGW'` && {
# Before running chkconfig.sed, remove the trailing '\r'
# characters that can bugger up various versions of sed.
tr -d '\r' < chkconfig.sed > chkconfig2.sed
mv -f chkconfig2.sed chkconfig.s
Angus Leeming wrote:
Or maybe tr?
test `uname -s | grep 'MINGW'` && {
# Before running chkconfig.sed, remove the trailing '\r'
# characters that can bugger up various versions of sed.
tr -d '\r' < chkconfig.sed > chkconfig2.sed
mv -f chkconfig2.sed chkconfig.s
Lars Gullik Bjønnes wrote:
Angus> This applies to both the 1.3.x and 1.4.x trees. It turns out
Angus> that the standard vesions of sed on Windows can't cope with
Angus> DOS-style line endings in sed scripts. The chkconfig.sed script
Angus> that is produced by chkconfig.ltx contains these DOS line
Angus Leeming <[EMAIL PROTECTED]> writes:
| Jean-Marc Lasgouttes wrote:
>> Angus> This applies to both the 1.3.x and 1.4.x trees. It turns out
>> Angus> that the standard vesions of sed on Windows can't cope with
>> Angus> DOS-style line endings in sed scripts. The chkconfig.sed script
>> Angus> t
Jean-Marc Lasgouttes wrote:
Angus> This applies to both the 1.3.x and 1.4.x trees. It turns out
Angus> that the standard vesions of sed on Windows can't cope with
Angus> DOS-style line endings in sed scripts. The chkconfig.sed script
Angus> that is produced by chkconfig.ltx contains these DOS lin
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> This applies to both the 1.3.x and 1.4.x trees. It turns out
Angus> that the standard vesions of sed on Windows can't cope with
Angus> DOS-style line endings in sed scripts. The chkconfig.sed script
Angus> that is produced by chkcon
This applies to both the 1.3.x and 1.4.x trees.
It turns out that the standard vesions of sed on Windows can't cope with
DOS-style line endings in sed scripts. The chkconfig.sed script that is
produced by chkconfig.ltx contains these DOS line endings.
The fix is simple. Immediately before thi
12 matches
Mail list logo
