[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (gnu)sed in texinfo
From: |
Mojca Miklavec |
Subject: |
Re: (gnu)sed in texinfo |
Date: |
Tue, 8 Jul 2014 09:00:55 +0200 |
On Mon, Jul 7, 2014 at 11:51 PM, Karl Berry wrote:
> Not executing run_recode() seems to work fine with the input
> file/for the failure I experienced.
>
> Good.
>
> I still believe making sed configurable at build time
>
> That would have the significant downsides of not making texi2dvi not
> being runnable without a configure step, and equally, not being
> copyable/usable on different systems. So I don't want to do that.
>
> What I did do was:
> (a) elminate all the recode stuff;
> (b) change all the sed calls to use $SED; defaults to sed, just like
> EGREP, etc. Distributors can change that variable assignment if they
> need some sed other than "sed".
Thank you very much. That should make MacPorts perfectly happy.
We can also easily patch that line with SED assignment if the need arises.
Mojca
- Re: (gnu)sed in texinfo, (continued)
- 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, 2014/07/04
- 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 <=