Re: removal proposal: emacs26 and emacs27 (and -nox11 variants)

[Greg Troxel <gdt%lexort.com@localhost>]

Makoto Fujiwara <makoto%if.t.u-tokyo.ac.jp@localhost> writes:

> For proposal of removing emacs26, honestly speaking:
>  - I'm still using emacs26 with some PC
>  - but it is kind of coming from my laziness
>  - and I have to setup either emacs28 with emacs29 anyway

I used to be in that sort of situation, but with the recent security
advisory I jumped to 29.4 immediately, and it was painless (other than
remove/rebuild).

> So, I'm incliend to accept this situation. But
> noticing devel/apel is failing due to missing emacs26/27.
>
> above emotion has become changed.
>
> I'm using
>   mail/wanderlust as for MUA, with
>   devel/apel,
>   devel/semi
>   editor/emacs26.
> The versions of these may not be of pkgsrc proper,
> say, with some local-mod, (which said local, but may be found somewhere
> at my repository on github (makoto-fujiwara) etc).
>
> In short, please keep emacs26 by the time when apel/semi/wanderlust
> lines are all packaged fine ?

I don't mean to push hard on this.  I was genuinely thinking there are
no good reasons and thus proposing is fine, and we see if there are good
reasons.

I would like us to be moving to removing old ones.  As I understand it:

26	first released 2018-05-28
27	first released 2020-08-10
28	first released 2022-04-04
29	first released 2023-07-30, currently maintained

so 26 is coming up on "people have had 4 years to migrate off it", based
on 27 release date.


Could you try to build those with emacs28 and post issues?