4.1.0-dev-1

4.1.0-dev-1

[Peter Stephenson]

I've just uploaded
  ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.gz
  ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.bz2

which uses autoconf 2.50 as promised.

This includes the line number changes for trial --- more environments have
their own local line numbering; see if you prefer it this way.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

Re: 4.1.0-dev-1

[Andrej Borsenkow]

On Mon, 9 Jul 2001, Peter Stephenson wrote:

> I've just uploaded
>   ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.gz
>   ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.bz2
>
> which uses autoconf 2.50 as promised.
>

Does it mean we may finally forget about 2.13 compatibility in HEAD?

Anyway, do not forget you need -C for config.cache now and better remove
old one.

-andrej

Re: 4.1.0-dev-1

[Peter Stephenson]

Andrej Borsenkow wrote:
> On Mon, 9 Jul 2001, Peter Stephenson wrote:
> 
> > I've just uploaded
> >   ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.gz
> >   ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.bz2
> >
> > which uses autoconf 2.50 as promised.
> >
> 
> Does it mean we may finally forget about 2.13 compatibility in HEAD?

We can't be sure everybody who uses the archive has upgraded yet.  I'd be
happy about printing a warning if the older version is being used, though.
I can't remember how to do at when autoconf rather than configure runs.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

Re: 4.1.0-dev-1

[Andrej Borsenkow]

Peter Stephenson wrote:

> Andrej Borsenkow wrote:
> 
>>On Mon, 9 Jul 2001, Peter Stephenson wrote:
>>
>>
>>>I've just uploaded
>>>  ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.gz
>>>  ftp://ftp.zsh.org/zsh/development/zsh-4.1.0-dev-tar.bz2
>>>
>>>which uses autoconf 2.50 as promised.
>>>
>>>
>>Does it mean we may finally forget about 2.13 compatibility in HEAD?
>>
> 
> We can't be sure everybody who uses the archive has upgraded yet.  I'd be
> happy about printing a warning if the older version is being used, though.
> I can't remember how to do at when autoconf rather than configure runs.
> 
> 



There is no way to print a warning, but AC_PREREQ(2.50) will abort if 
autoconf version is less then specified. configur.ac already have it. 
Actually, if we remove configure.in older versions simply choke by default.


-andrej

Re: 4.1.0-dev-1

[Bart Schaefer]

On Jul 9, 10:08pm, Andrej Borsenkow wrote:
} Subject: Re: 4.1.0-dev-1
}
} There is no way to print a warning, but AC_PREREQ(2.50) will abort if 
} autoconf version is less then specified. configur.ac already have it. 
} Actually, if we remove configure.in older versions simply choke by default.

The point is that we don't want to choke, we just want to let people know
that they ought to upgrade.

I personally would be annoyed if 2.13 compatibilty suddenly went away.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net