[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (gnu)sed in texinfo
From: |
Mihai Moldovan |
Subject: |
Re: (gnu)sed in texinfo |
Date: |
Sat, 05 Jul 2014 01:59:33 +0200 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
* On 05.07.2014 01:35 am, Karl Berry wrote:
> If you comment out the call to run_recode(), does it solve your problem?
> (Please don't educate me about how this doesn't deal with the "real"
> issue. :)
I'll check that. There may be more invocations of sed failing, so I can not give
a clear answer without testing. Will reply later.
> It still seems to me that getting a better sed on your system would help
> many more people than just worrying about a Texinfo-specific script.
We do have gnused and likely every machine with MacPorts has that port
installed. However, we do not add the gnubin prefix to $PATH (that is, a prefix
where symlinks with the "g" prefix removed reside in -- like sed ->
${install_prefix}/bin/gsed, df -> ${install_prefix}/bin/gdf etc.) when compiling
software, as the general policy is to use the system provided tools whenever
possible.
This mostly works fine and is sane to keep dependencies low.
Mihai
smime.p7s
Description: S/MIME Cryptographic Signature
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/04
- Re: (gnu)sed in texinfo, Mojca Miklavec, 2014/07/04
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/04
- Re: (gnu)sed in texinfo, Karl Berry, 2014/07/04
- Re: (gnu)sed in texinfo,
Mihai Moldovan <=
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/04
- Re: (gnu)sed in texinfo, Karl Berry, 2014/07/07
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/07
- Re: (gnu)sed in texinfo, Mojca Miklavec, 2014/07/08