emacs: updated emacsen-common, new emacs28 and emacs30

[PovlAbrahamsen]

This pull request contains several changes:

• disabled emacs23 through emacs26 on Arm. They do not currently pass the configure stage.
• bumped revisions and added conflicts/replaces with new versions up to emacs30 to all previous infofiles
• updated emacsen-common to the latest version from Debian. This addresses several warnings in emacs30, and has various other changes/improvements. emacs28 still works with the previous version.
• added emacs28-nox and emacs30-nox
  • we won't be able to build versions of emacs28 and above for X11 until we have GTK+2 >= 2.24 in Fink. The X11 options have been left in the infofile for future use, but have not been tested.
  • JIT compilation using libgccjit is not enabled in emacs30

I have tested on MacOS 15.6, Apple Silicon, XCode 16.4. I've tried various combinations of upgrading and downgrading emacsen-common and emacs packages (though only emacs28-nox and emacs30-nox build on Arm) - and it seems robust! I have not tested on Intel, or with older versions of emacs.

There are various warnings about the scripts calling install-info - but the infofiles seem to work correctly.

[nieder]

For me on 13.7/x86_64 with only emac26 installed, the installed versions are in the physical file %p/var/lib/emacsen-common/installed-flavors. The above .../state/flavor/installed/... path doesn't exist. Is this path something that started with emacs28 and/or emacsen-common-3 ?

[PovlAbrahamsen]

Yes, emacsen-common 3 changes from a single file %p/var/lib/emacsen-common/installed-flavors to a folder %p/var/lib/emacsen-common/state/flavor/installed/, containing a file for each variant. The update should convert from the old format to the new (via %p/var/lib/emacsen-common/state/flavor/pending/).

[dmacks]

The enums bug is solved by emacs-mirror/emacs@222b597

But still FTBFS on ARM with

Dumping under the name emacs
unexec: my_edata is not in section __data

followed by a core-dump. I definitely support getting the new version moving along and masking out older ones that do not build on newer platforms until someone figures them out. I'm disappointed we won't have an x11 option, but again "better is better, even if not perfect".

Added note: leads for possible work-around to the unexec fail:

• https://news.ycombinator.com/item?id=21394916
• https://emacs.stackexchange.com/questions/43894/compiling-emacs-without-dump-unexec-enabled

[dmacks]

f7c91fb fixes the emacs26 build on ARM/Tahoe. The x11 variant does not display well for me, but lots of things are not displaying correctly for me even in regular Terminal windows (emacs itself does). Is it worth backporting this to older emacsen?

[dmacks]

For the record, XQuartz itself is partially broken on Tahoe. See XQuartz/XQuartz/issues/438 among others.