Page MenuHomeFreeBSD

editors/emacs: WIP to prepare for imminent 30.1 release
Needs ReviewPublic

Authored by jrm on Sat, Jan 11, 9:03 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jan 18, 7:23 AM
Unknown Object (File)
Fri, Jan 17, 5:58 PM
Unknown Object (File)
Thu, Jan 16, 1:22 AM
Subscribers
None

Details

Reviewers
yasu
ashish

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 61676
Build 58560: arc lint + arc unit

Event Timeline

jrm requested review of this revision.Sat, Jan 11, 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>.