Page MenuHomeFreeBSD

editors/emacs: Update to 30.1
ClosedPublic

Authored by jrm on Jan 11 2025, 9:03 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 4, 7:04 PM
Unknown Object (File)
Thu, Feb 27, 4:20 AM
Unknown Object (File)
Tue, Feb 25, 12:47 AM
Unknown Object (File)
Mon, Feb 24, 9:55 PM
Unknown Object (File)
Mon, Feb 24, 9:33 PM
Unknown Object (File)
Mon, Feb 24, 8:47 AM
Unknown Object (File)
Wed, Feb 5, 9:50 PM
Unknown Object (File)
Feb 4 2025, 2:10 AM
Subscribers
None

Details

Summary

The updated Canna patches were created by HIROSE yuuji <yuuji@gentei.org>.

Release announcement:   https://lists.gnu.org/archive/html/info-gnu-emacs/2025-02/msg00009.html
Sponsored by:           The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D48432

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jrm requested review of this revision.Jan 11 2025, 9:03 PM
jrm created this revision.

Remove extra SUB_LIST=...

  1. @yasu, are you able to handle updating the canna patch?
  1. I turned NATIVECOMP on by default. What do you think? I've been running it for years, and it's been stable. Are there still issues compiling some packages? I haven't encountered any, but I also didn't do any research. If there are no known issues, should we remove pkg-message?
In D48432#1104894, @jrm wrote:
  1. @yasu, are you able to handle updating the canna patch?

Ok, I'll request it to author after 30.1 is released.

  1. I turned NATIVECOMP on by default. What do you think? I've been running it for years, and it's been stable. Are there still issues compiling some packages? I haven't encountered any, but I also didn't do any research. If there are no known issues, should we remove pkg-message?

Upstream enabled native compilation by default with emacs-30 branch. So we should follow it.
As for pkg-message, I think we should keep it for a while. For most users of editors/emacs 30.1 will be there first experience with native compilation. So they may face issue with it and it may be helpful for them to provide workaround to disable it with user settings. For example, how about keeping pkg-message until it is updated to Emacs 31?

In D48432#1104894, @jrm wrote:
  1. @yasu, are you able to handle updating the canna patch?

Ok, I'll request it to author after 30.1 is released.

I incorrectly recalled that you had updated the patch in the past. Since it's just a matter of communication, I'll send emails.

  1. I turned NATIVECOMP on by default. What do you think? I've been running it for years, and it's been stable. Are there still issues compiling some packages? I haven't encountered any, but I also didn't do any research. If there are no known issues, should we remove pkg-message?

Upstream enabled native compilation by default with emacs-30 branch. So we should follow it.
As for pkg-message, I think we should keep it for a while. For most users of editors/emacs 30.1 will be there first experience with native compilation. So they may face issue with it and it may be helpful for them to provide workaround to disable it with user settings. For example, how about keeping pkg-message until it is updated to Emacs 31?

Sounds good. Thank you.

Incorporate updated Canna patches from HIROSE yuuji <yuuji@gentei.org>.

Mk/Uses: Update EMACS_VER to 30.1

jrm retitled this revision from editors/emacs: WIP to prepare for imminent 30.1 release to editors/emacs: Update to 30.1.Mon, Feb 24, 1:42 AM

Emacs 30.1 is released. I will put the PORTREVISION bumps in a separate review. Minor changes will be required when HIROSE yuuji updates the canna patch.

jrm edited the summary of this revision. (Show Details)

Update Canna patches

This revision was not accepted when it landed; it landed in state Needs Review.Mon, Feb 24, 9:45 PM
This revision was automatically updated to reflect the committed changes.