David R.Morrison wrote:
As mentioned on the new preparing for 10.5 page on the fink wiki,
echo -n is now deprecated in fink. I have edited the vast majority
of packages where this occurs to conform to the new version. Instead of
echo -n string
one should now write
/bin/echo
On Dec 17, 2006, at 6:02 PM, Martin Costabel wrote:
David R.Morrison wrote:
As mentioned on the new preparing for 10.5 page on the fink wiki,
echo -n is now deprecated in fink. I have edited the vast majority
of packages where this occurs to conform to the new version.
Instead of
On Dec 17, 2006, at 08:10, Peter O'Gorman wrote:
So you can probably assume that if there are differences between the
UNIX03 spec and bsd, then Apple will probably go with UNIX03.
If the shell is invoked as /bin/sh, it will be in standards-
compliant sh mode, and echo won't interpret -n. If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-François Mertens wrote:
I see coreutils is at version 6.7, vs 5.96 in fink.
If the maintainer were willing to update, I would hope the need for
the /bin/
to disappear ... ; there should be a way to write things
'portably' (at least
As mentioned on the new preparing for 10.5 page on the fink wiki,
echo -n is now deprecated in fink. I have edited the vast majority
of packages where this occurs to conform to the new version. Instead of
echo -n string
one should now write
/bin/echo string\c
(See man echo.) This
I see coreutils is at version 6.7, vs 5.96 in fink.
If the maintainer were willing to update, I would hope the need for
the /bin/
to disappear ... ; there should be a way to write things
'portably' (at least
across current versions of GNU and of Darwin...).
It is a bit of a shock to see
On Dec 17, 2006, at 8:49 AM, David R.Morrison wrote:
As mentioned on the new preparing for 10.5 page on the fink wiki,
echo -n is now deprecated in fink. I have edited the vast majority
of packages where this occurs to conform to the new version.
Instead of
echo -n string
one
The reason for the /bin has to do with behaviors of different shells
in Tiger. Without writing /bin/echo, the 'echo' command is processed
as a shell built-in, and the results are different for bash and tcsh.
-- Dave
On Dec 16, 2006, at 5:00 PM, Jean-François Mertens wrote:
I see
On 17 Dec 2006, at 02:38, David R. Morrison wrote:
The reason for the /bin has to do with behaviors of different
shells in Tiger. Without writing /bin/echo, the 'echo' command is
processed as a shell built-in, and the results are different for
bash and tcsh.
You're completely right !
On 17 Dec 2006, at 02:00, Jean-François Mertens wrote:
I see coreutils is at version 6.7, vs 5.96 in fink.
If the maintainer were willing to update, I would hope the need for
the /bin/
to disappear ... ; there should be a way to write things
'portably' (at least
across current versions
On Dec 17, 2006, at 11:11 AM, Jean-François Mertens wrote:
It is also okay to use printf -
% printf string
http://www.opengroup.org/onlinepubs/95399/utilities/printf.html
the doc cited is a bit painful to read through...
and 'man printf' doesn't show at all 9at first sight at least)
David == David R Morrison [EMAIL PROTECTED] writes:
David As mentioned on the new preparing for 10.5 page on the fink wiki,
David echo -n is now deprecated in fink. I have edited the vast majority
David of packages where this occurs to conform to the new version. Instead of
Davidecho
On 17 Dec 2006, at 04:44, Peter O'Gorman wrote:
There is a /usr/bin/printf for shells where it is not available as a
builtin, so in tcsh printf works too, but it uses /usr/bin/printf.
printf(1) behaves in a very similar way to the printf(3) function.
You can, for example do:
% printf The
On Dec 16, 2006, at 6:11 PM, Jean-François Mertens wrote:
On 17 Dec 2006, at 02:38, David R. Morrison wrote:
The reason for the /bin has to do with behaviors of different
shells in Tiger. Without writing /bin/echo, the 'echo' command is
processed as a shell built-in, and the results
14 matches
Mail list logo
