[OE-core] [PATCH] vim: update from 8.1.1518 to 8.2.0110

Tom Rini trini at konsulko.com
Thu Jan 16 17:02:48 UTC 2020


On Tue, Jan 14, 2020 at 11:18:44PM +0100, Alexander Kanavin wrote:
> On Tue, 14 Jan 2020 at 21:10, Randy MacLeod <randy.macleod at windriver.com>
> wrote:
> 
> > Oleg is getting started using Yocto so I'll reply on his behalf since
> > I asked him to update vim as his first commit.
> >
> > I'm not sure what you mean by 8.2. Are you talking about calling the
> > recipe:
> >     vim_8.2.bb
> > instead of vim_8.2.0110.bb?
> >
> > Vim tags on a daily or more frequent basis. Are you saying that we
> > should keep the
> > same SRCREV for 8.2.0110 but use a different name?
> >
> > I looked at:
> >     git log v8.2.0000..v8.2.0118
> > and all the commits seem to fix bugs so I prefer to take this tested
> > v8.2.0110
> > update and update vim every month or two so that we get the latest fixes.
> >
> 
> Vim adds a tag for every single commit they make, fixes or not, so this
> approach would in effect be updating to random development snapshots. I
> would rather have a more conservative update strategy, and update to the
> original 8.2 release. If you look at the homepage, 8.2 is the version they
> announced as the new release: https://www.vim.org/
> 
> That's also what 'devtool latest-version vim' should currently report and
> 'devtool upgrade' upgrade to: I purposely cut off the point releases and
> left only the major.minor part there.

What we had talked about before was trying to follow (more or less)
updating to versions that one of the desktop distros had chosen, to
avoid the fact that yes, every commit to vim is a new version number
thus making it hard to know what's an important/good release but also
still getting bug fixes and so forth.

-- 
Tom


More information about the Openembedded-core mailing list