Page MenuHomeFreeBSD

editors/emacs-devel: Update to 28.0.50
ClosedPublic

Authored by ashish on Jan 2 2020, 10:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 4 2024, 11:45 AM
Unknown Object (File)
Jan 31 2024, 1:37 AM
Unknown Object (File)
Jan 31 2024, 1:37 AM
Unknown Object (File)
Jan 31 2024, 1:37 AM
Unknown Object (File)
Jan 31 2024, 1:37 AM
Unknown Object (File)
Jan 31 2024, 1:37 AM
Unknown Object (File)
Jan 31 2024, 1:37 AM
Unknown Object (File)
Jan 31 2024, 1:36 AM
Subscribers

Details

Summary

Since this differential contains a major version bump, so we need to update Mk/Uses/emacs.mk too, and bump the versions of dependent ports as well. Following notes w.r.t. the differential:

  1. Bump to mail/notmuch port: As mail/notmuch-emacs is a slave port, so PORTREVISION bump will get overridden by PORTREVISION value present in its master port (mail/notmuch) so which is why I switched it to ?=
  1. Bump to japanese/mozc-server port: Same as #1, except japanese/mozc-el is the slave port which is needing PORTREVISION bump
Test Plan

Poudriere build

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 28493
Build 26550: arc lint + arc unit

Event Timeline

Ashish wrote:

Also since we are bumping dependent ports, do you think we should still add UPDATING entry similar to your message above ?

We do, otherwise pkg upgrade will not upgrade foo-emacs27 packages.

# sh
# for i in $(pkg query -g %n '*-emacs27'); do pkg set -yn ${i}:${i%-emacs27}-emacs28; done
# pkg upgrade
  • Added an UPDATING entry
  • Updated port version to latest git revision
  • Minor correction to UPDATING entry
  • Update to latest git revision
  • Fix UPDATING message
UPDATING
15–18

Sorry, I missed a case here. We need this to correctly handle packages like tablist-emacs27_nox-1.0_1.

# sh
# for i in $(pkg query -g %n '*-emacs27*'); do nn=$(echo "$i" | sed -e 's/emacs27/emacs28/'); pkg set -yn "$i":"$nn"; done;
# pkg upgrade
  • Revise UPDATING entry to account for another use case.
This revision was not accepted when it landed; it landed in state Needs Review.Jan 7 2020, 4:56 AM
This revision was automatically updated to reflect the committed changes.