bug-apl
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU APL 1.9 Released


From: Dr . Jürgen Sauermann
Subject: Re: GNU APL 1.9 Released
Date: Wed, 10 Jul 2024 12:33:15 +0200
User-agent: Mozilla Thunderbird

I was not aware that I am using html emails.
If you have problems viewing GNU ASPL posts then
you can find all of them here:

https://lists.gnu.org/archive/html/bug-apl/


On 7/9/24 19:55, enztec@gmx.com wrote:
btw glad to see you quite using html email
now i can read your replies


On Thu, 4 Jul 2024 13:12:47 +0200
Dr. Jürgen Sauermann <mail@xn--jrgen-sauermann-zvb.de> wrote:

That is correct.

A GNU APL release is the state of the software at a point in time where
it is stable.
Stable means that all major trouble reports are fixed and no new
functionality is
planned or in progress.

It is also a synchronization point in the sense that the lifetime of the
previous release
has ended. That implies that trouble reports on older releases will not
be accepted
unless the problem reported still exists in the latest release.
glad to see you fixed
the make clean  and make distclean problems that were there for years

that doesn't include the libapl problems?
On 7/3/24 23:36, enztec@gmx.com wrote:
so it is really 2 weeks stable release?

On Mon, 1 Jul 2024 12:08:50 +0200dp
Dr. Jürgen Sauermann <mail@xn--jrgen-sauermann-zvb.de> wrote:

Hi,

yes it is a snapshot of the current SVN.
No need to do anything if you update via SVN.

Best Regards,
Jürgen


On 6/30/24 18:55, enztec@gmx.com wrote:
Hi,

is this apl-1.9.tar.gz just a tar.gz of the current svn or something labelled 
as a reak 'stable' release?

since i assume you will be doing 'releases' from now on (?) - maybe calling it 
apl-2.0 would have been a better version number to start this new release 
scheme with rather then apl-1.9?

a suggestion - add something to the configure summary to make note what the 
configure was for - libapl or python3/lib_gnu_apl etc
like you are doing with     apl_POSTGRES:
apl_APL:     [yes/no]
apl_LIBAPL:  [yes/no]
apl_PYTHON:  [yes/np]

configure --with-python -> your Makefile.am is 'hardcoded' for 
'-I/usr/include/python3.6m -I/usr/include/python3.8'
i didn't see any information for compiling with different python versions and 
installation locations (for Python.h) that would require using CPPFLAGS for 
different installation locations and newer python versions
configure CPPFLAGS='-I/usr/local/include/python3.10' ......     for my 
particular python3.10 installation



On Sun, 30 Jun 2024 13:41:38 +0200
Dr. Jürgen Sauermann <mail@xn--jrgen-sauermann-zvb.de> wrote:

Hi,

I am happy to announce that *GNU APL 1.9* has been released.

GNU APL is a free implementation of the ISO standard 13751 aka.
"Programming Language APL, Extended".

The 1.9 release contains:

* Bug fixes


Have fun!

Dr. Jürgen Sauermann
Author and Maintainer of GNU APL


P.S. Some redundant distribution formats of GNU APL  (RMPs, windows)
are no longer supported. The best way of using GNU APL is to fetch it from
the savannah SVN and GIT archives (see https://www.gnu.org/software/apl ).
These archives are, unlike the less frequent GNU APL releases, always
up-to-date and in sync with the ongoing GNU APL development.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]