> From: Eric Siegerman <[EMAIL PROTECTED]>
> Date: Thu, 1 Aug 2002 13:46:05 -0400
>
> Looks good, except that the leading "." to pacify zsh got lost
> in the shuffle.
The zsh "." issue is still in there, though a bit terser.
> > -$unset CDPATH || CDPATH=:
> > +$unset CDPATH || CDPATH=$PATH_SEPA
David A. Holland wrote on 1 Aug 2002:
> Dan Kegel wrote on 18 Dec 2001:
> > Currently, netkit
> > (ftp://ftp.uk.linux.org/pub/linux/Networking/netkit/netkit-combo-0.17.tar.gz)
> > uses a configure script (good!) but it's not autoconf-generated.
>
> Correct.
>
> > This is a problem when cro
On Thu, Aug 01, 2002 at 07:20:33AM -0700, Paul Eggert wrote:
> -Setting @code{CDPATH} to the empty value is not enough for most shells.
> -A simple path separator is enough except for @code{zsh}, which prefers a
> -leading dot:
> [...]
> +To work around the problem, Autoconf-generated scripts unse
> From: "Mark D. Roth" <[EMAIL PROTECTED]>
> Date: Thu, 25 Jul 2002 08:25:39 -0500
>
> The -P option isn't listed in the ksh docs under Solaris or AIX.
> Only OpenBSD seems to document this.
It's also documented in Bash 2.05b. This feature was recently added
to Bash (presumably in response to P
>>> "Bob" == Bob Ham <[EMAIL PROTECTED]> writes:
[...]
Bob> Any idea when 1.7 will be released (roughly, obviously; I
Bob> mean, months? weeks? days?) I've got a build tree in a
Bob> cvs that uses cvs automake. It's waiting for 1.7 until
Bob> it's committed :)
CVS Automake needs Autocon
