vim: update from 8.1.1518 to 8.2.0110
PATCH 1/1 vim: update from 8.1.1518 to 8.2.0110
vim-tiny: update from 8.1.1518 to 8.2.0110
The date in the license was updated to 2020 and
a trailing space was removed from one line.
---
.../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} | 0
meta/recipes-support/vim/vim.inc | 4 ++--
meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} | 0
3 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} (100%)
rename meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} (100%)meta/recipes-support/vim/vim-tiny_8.2.0110.bb renamed from meta/recipes-support/vim/vim-tiny_8.1.1518.bb +0 -0
meta/recipes-support/vim/vim.inc +2 -2
@@ -5,14 +5,14 @@ DEPENDS = "ncurses gettext-native" # vimdiff doesn't like busybox diff RSUGGESTS_${PN} = "diffutils" LICENSE = "vim" -LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=f1f82b42360005c70b8c19b0ef493f72" +LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=909f1394892b7e0f9c2a95306c0c552b" SRC_URI = "git://github.com/vim/vim.git \ file://disable_acl_header_check.patch \ file://vim-add-knob-whether-elf.h-are-checked.patch \ file://0001-src-Makefile-improve-reproducibility.patch \ " -SRCREV = "202d982b36d87cf91d992bd7e30d3223bdc72cd9" +SRCREV = "e05a89ac6399a8c7d164c99fdab6841d999a9128" # Do not consider .z in x.y.z, as that is updated with every commit UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+\.\d+)\.0"
meta/recipes-support/vim/vim_8.2.0110.bb renamed from meta/recipes-support/vim/vim_8.1.1518.bb +0 -0
Signature · 1 line
2.23.0
Can you update to just 8.2 please? 0110 is an arbitrary commit as vimupstream adds a version tag for each of the commits.
Alex
Quoted 52 lines · Oleg Polyakov
vim-tiny: update from 8.1.1518 to 8.2.0110
The date in the license was updated to 2020 and
a trailing space was removed from one line.Signed-off-by Oleg Polyakov <[email protected]>---
.../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} | 0 meta/recipes-support/vim/vim.inc | 4 ++-- meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} | 0 3 files changed, 2 insertions(+), 2 deletions(-)rename meta/recipes-support/vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} (100%) rename meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} (100%)
meta/recipes-support/vim/vim-tiny_8.2.0110.bb renamed from meta/recipes-support/vim/vim-tiny_8.1.1518.bb +0
-0meta/recipes-support/vim/vim.inc +0
-0@@ -5,14 +5,14 @@ DEPENDS = "ncurses gettext-native" # vimdiff doesn't like busybox diffRSUGGESTS_${PN} = "diffutils"
LICENSE = "vim"meta/recipes-support/vim/vim.inc +1
-1-LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=f1f82b42360005c70b8c19b0ef493f72" +LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=909f1394892b7e0f9c2a95306c0c552b"SRC_URI = "git://github.com/vim/vim.git \ file://disable_acl_header_check.patch \ file://vim-add-knob-whether-elf.h-are-checked.patch \ file://0001-src-Makefile-improve-reproducibility.patch \"
meta/recipes-support/vim/vim.inc +1
-1-SRCREV = "202d982b36d87cf91d992bd7e30d3223bdc72cd9" +SRCREV = "e05a89ac6399a8c7d164c99fdab6841d999a9128"# Do not consider .z in x.y.z, as that is updated with every commit
UPSTREAM_CHECK_GITTAGREGEX= "(?P<pver>\d+\.\d+)\.0"meta/recipes-support/vim/vim_8.2.0110.bb renamed from meta/recipes-support/vim/vim_8.1.1518.bb +0
-0Signature · 7 lines
2.23.0 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 1 line · Alexander Kanavin
Can you update to just 8.2 please? 0110 is an arbitrary commit as vimupstream adds a version tag for each of the commits.
Hi Alex,
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.
../Randy
Quoted 55 lines
Alex
Quoted 52 lines · Oleg Polyakov
vim-tiny: update from 8.1.1518 to 8.2.0110
The date in the license was updated to 2020 and
a trailing space was removed from one line.Signed-off-by Oleg Polyakov <[email protected]>---
.../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} | 0 meta/recipes-support/vim/vim.inc | 4 ++-- meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} | 0 3 files changed, 2 insertions(+), 2 deletions(-)rename meta/recipes-support/vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} (100%) rename meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} (100%)
meta/recipes-support/vim/vim-tiny_8.2.0110.bb renamed from meta/recipes-support/vim/vim-tiny_8.1.1518.bb +0
-0meta/recipes-support/vim/vim.inc +0
-0@@ -5,14 +5,14 @@ DEPENDS = "ncurses gettext-native" # vimdiff doesn't like busybox diffRSUGGESTS_${PN} = "diffutils"
LICENSE = "vim"meta/recipes-support/vim/vim.inc +1
-1-LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=f1f82b42360005c70b8c19b0ef493f72" +LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=909f1394892b7e0f9c2a95306c0c552b"SRC_URI = "git://github.com/vim/vim.git \ file://disable_acl_header_check.patch \ file://vim-add-knob-whether-elf.h-are-checked.patch \ file://0001-src-Makefile-improve-reproducibility.patch \"
meta/recipes-support/vim/vim.inc +1
-1-SRCREV = "202d982b36d87cf91d992bd7e30d3223bdc72cd9" +SRCREV = "e05a89ac6399a8c7d164c99fdab6841d999a9128"# Do not consider .z in x.y.z, as that is updated with every commit
UPSTREAM_CHECK_GITTAGREGEX= "(?P<pver>\d+\.\d+)\.0"meta/recipes-support/vim/vim_8.2.0110.bb renamed from meta/recipes-support/vim/vim_8.1.1518.bb +0
-0Signature · 7 lines
2.23.0 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 2 lines
# Randy MacLeod # Wind River Linux
Quoted 12 lines · Randy MacLeod
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.bbinstead 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?
Quoted 6 lines
I looked at:
git log v8.2.0000..v8.2.0118and 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.
Alex
Quoted 22 lines · Alexander Kanavin
On Tue, 14 Jan 2020 at 21:10, Randy MacLeod <[email protected] <mailto:[email protected]>> 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 <http://vim_8.2.bb>
instead of vim_8.2.0110.bb <http://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.
Quoted 1 line
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/
Sure, that's fine for now. Most of the commits are bug fixes after 8.2 but we don't need to worry about any of them now and I guess if we stick with this approach, and say there as a CVE for vim that we wanted to fix, we'd just backport the single commit rather than bump the version to 8.2.1248 or some such version.
Quoted 2 lines
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.
Right. This will also give Oleg an excuse to try 'devtool upgrade' to compare manually upgrading. :)
../Randy
Quoted 2 lines
Alex
Signature · 2 lines
# Randy MacLeod # Wind River Linux
Quoted 7 lines · Randy MacLeod
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.
Right. This will also give Oleg an excuse to try 'devtool upgrade' to compare manually upgrading. :)
Thanks, that is of course appreciated. Run 'devtool check-upgrade-status' to get an overview of what needs updating, maybe you can help Oleg to pick the easier updates from that list.
Alex
Quoted 28 lines · Alexander Kanavin
Quoted 12 lines · Randy MacLeod
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.bbinstead 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?Quoted 6 lines
I looked at:
git log v8.2.0000..v8.2.0118and 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/
Quoted 3 lines
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.
Signature · 1 line
Tom