> -----Original Message-----
> From: Alexander Kanavin <[email protected]>
> Sent: Tuesday, February 24, 2026 18:19
> To: Marko, Peter (FT D EU SK BFS1) <[email protected]>
> Cc: [email protected]; Yoann Congal
> <[email protected]>
> Subject: Re: [OE-core][PATCH] vim: upgrade 9.1.2144 -> 9.2.0
> 
> On Tue, 24 Feb 2026 at 17:45, Peter Marko via lists.openembedded.org
> <[email protected]> wrote:
> > Alternatively, we could also continue updating vim in LTS like we did in 
> > the past.
> > For now, there are two active CVEs in LTS releases.
> > Please let me know if I need to backport patches now or if vim upgrade 
> > would be
> accepted.
> >
> > Any thoughts from the maintainers?
> 
> In the past we tried backporting CVE patches to vim for some time.
> Then it became clear that approach is unsustainable.
> 
> But I have a different thought. Let's drop vim from oe-core and
> replace it with nano :)
> 
> Benefits:
> - sane version policy, not that many (probably none) CVEs
> - it's the only editor that doesn't annoy me :)
> 
> Nano is already in meta-oe, if you support the idea, can you prepare
> the patches to move it here?

Appealing... quick grep in oe-core shows it would be possible.
Nothing really depending on it, diffoscope being the only one which would have 
to be looked at.

But I think that vim is still something that users would like to have (I 
personally prefer it over both nano and vi).
So it would be moved to meta-oe, dumping the CVE work on them (Gyorgy?), not 
really helping the ecosystem.
Also nano has the dreaded GPL-3...
And the benefits would be seen only in 2 years after scarthgap would go EOL so 
not solving the immediate question at hand.


Peter

> 
> Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#231899): 
https://lists.openembedded.org/g/openembedded-core/message/231899
Mute This Topic: https://lists.openembedded.org/mt/117978611/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to