Re: [update] emacs-26.1

On Wed, May 30, 2018 at 07:04:46PM +0200, Jeremie Courreges-Anglas wrote:
> On Wed, May 30 2018, kwesterback@gmail.com wrote:
> >> On May 30, 2018, at 7:55 AM, Jeremie Courreges-Anglas <jca@wxcvbn.org> wrote:
> >>
> >>> On Tue, May 29 2018, Jeremie Courreges-Anglas <jca@wxcvbn.org> wrote:
> >>> So emacs-26.1 has been released yesterday:
> >>>
> >>> https://lists.gnu.org/archive/html/emacs-devel/2018-05/msg00765.html
> >>>
> >>> I doubt that this update addresses the bug encountered by Gr??goire,
> >>> Piotr and Manuel, but I don't think it will make it worse.
> >>>
> >>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29170
> >>>
> >>> I have only built and tested this on amd64 so far, I'll handle armv7
> >>> and sparc64 later. People running different archs and/or one of the
> >>> graphical flavors, your test reports are welcome!
> >>
> >> I could have mentioned that I intend to commit this soon. oks welcome too.
> >>
> >> --
> >> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
> >>
> >
> > Unfortunately my ports building setup has gotten into state where it's
> > taking > 3days to get to emacs. :-(.
>
> Looks like you're not the only one who sees an increase in build time.
> Anyway, you don't need to rebuild everything from scratch, and emacs
> itself is relatively quick to build.
>
> > But assuming this diff doesn't do
> > anything more than the rc1 diff I've been running for a while (gtk3,
> > amd64) then ok krw@
>
> Not too many changes in the code but lots of lines moved, still:
>
> ritchie /tmp$ wc -l emacs-26.1-rc1-to-emacs-26.1-tarball.diff
> 12435 emacs-26.1-rc1-to-emacs-26.1-tarball.diff
>
> ~jca/tmp/emacs-26.1-rc1-to-emacs-26.1-tarball.diff.gz if you want to
> take a look.
>
> --
> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE

More fun than I anticipated getting enough ports compiled that emacs
could compile. Including forgetting to use your latest diff at least
once. :-)

Once I got that far compiling the gtk+3 version went without incident
and the resulting port works at least as well as the RC1
version. i.e. nothing breaks in usage case.

so ok krw@ fwiw.

.... Ken