On 12/04/25 21:14, Camm Maguire wrote: > Greetings! > > "Chun Tian (binghe)" <[email protected]> writes: > >> Greetings! >> >> Congratulations for the initial release of GCL 2.7.x (I think the 2.7.0pre >> packages existed in Debian for at least 20 years). I will soon send a PR to >> MacPorts for the new "gcl27" package (based on your existing Port >> definition), >> with this additional patch, and (hopefully) also with changes from the >> gnu-build-system branch. >> > > gnu-build-system has been incorporated into the release tarball. Just > the errata known so far. I really appreciate your handling the macports > stuff if that works for you. But I do think the gcl repository should > be kept up to date with the latest working macports packaging info for > the day you may wish to retire.
Oh, that's great. This means the coming "gcl27" package on MacPorts will support
both cltl1 and ANSI modes, triggered by environment variables.
Of course, you can keep a copy of Ports definition with GCL source code. But the
MacPorts repository is always there holding not only the port definitions and
some extra patch files (which essentially comes from pre-release changes from
you).
>
>> Do you have release plans for GCL 2.6.15?
>
> Given the magnitude of the changes, I was thinking of a period where
> both systems could coexist for a while until it is clear that 2.7 is
> better in every respect, after which resorting to one package named gcl
> would be in order. Do you think a 2.6.15 release is needed or
> desirable? Is it a distraction?
At this moment I'm not sure 2.7 is really better in every respect. I saw you
were trying to build Debian "axiom" package by GCL 2.7 but it seems that
currently the Debian package is still based on GCL 2.6 (I don't have Debian sid
environment, only a Debian testing.)
If you can make a 2.6.15 release (and consider it's the last 2.6.x release), one
immediate good thing is that I can send a small PR to MacPorts to update
existing "gcl" package, such that it will work on more macOS versions (more than
what 2.6.14 can support). And I think it's good to have Axiom (ACL2, Maxima,
etc.) to support both GCL 2.6.15 and 2.7.1, and then people can compare on the
performance of these software under different GCL versions, to confirm if GCL
2.7 is really better in every respect.
--Chun
>
> Take care,
>
>>
>> --Chun
>>
>> On 12/04/25 05:34, Camm Maguire wrote:
>>> Greetings! While these tiny issues will likely not affect many if any,
>>> there are alas a few tiny errata with the 2.7.1 tarball release. Posted
>>> here just for those interested. Will of course be incorporated in the
>>> next release.
>>>
>>> =============================================================================
>>> modified gcl/debian/rules
>>> @@ -138,7 +138,7 @@ clean: debian/control debian/gcl.templates
>>> rm -rf $(INS) debian/substvars debian.upstream
>>> rm -rf *stamp build-indep
>>> rm -f debian/elpa-gcl$(EXT).elpa debian/gcl$(EXT)-pkg.el
>>> - rm -rf $(EXT_TARGS) info/gcl$(EXT)*.info*
>>> + rm -rf $(EXT_TARGS) info/gcl$(EXT)*.info* gcl_pool
>>>
>>> debian-clean: debian/control debian/gcl.templates
>>> dh_testdir
>>> modified gcl/git.tag
>>> @@ -1,2 +1,2 @@
>>> -"Version_2_7_0"
>>> +"Version_2_7_1"
>>>
>>> modified gcl/o/alloc.c
>>> @@ -707,6 +707,7 @@ empty_relblock(void) {
>>> for (;!rb_emptyp();) {
>>> tm_table[t_relocatable].tm_adjgbccnt--;
>>> expand_contblock_index_space();
>>> + expand_contblock_array();
>>> GBC(t_relocatable);
>>> }
>>> sSAleaf_collection_thresholdA->s.s_dbind=o;
>>> =============================================================================
>>>
>>> Take care,
>>>
>>
>
signature.asc
Description: OpenPGP digital signature
