* [PATCH v2] vim: update to 8.1.1097
@ 2019-03-31 15:50 Oleksandr Kravchuk
2019-03-31 20:11 ` Tom Rini
0 siblings, 1 reply; 7+ messages in thread
From: Oleksandr Kravchuk @ 2019-03-31 15:50 UTC (permalink / raw)
To: openembedded-core; +Cc: Oleksandr Kravchuk
Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
---
.../vim/{vim-tiny_8.1.1017.bb => vim-tiny_8.1.1097.bb} | 0
meta/recipes-support/vim/{vim_8.1.1017.bb => vim_8.1.1097.bb} | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/vim/{vim-tiny_8.1.1017.bb => vim-tiny_8.1.1097.bb} (100%)
rename meta/recipes-support/vim/{vim_8.1.1017.bb => vim_8.1.1097.bb} (98%)
diff --git a/meta/recipes-support/vim/vim-tiny_8.1.1017.bb b/meta/recipes-support/vim/vim-tiny_8.1.1097.bb
similarity index 100%
rename from meta/recipes-support/vim/vim-tiny_8.1.1017.bb
rename to meta/recipes-support/vim/vim-tiny_8.1.1097.bb
diff --git a/meta/recipes-support/vim/vim_8.1.1017.bb b/meta/recipes-support/vim/vim_8.1.1097.bb
similarity index 98%
rename from meta/recipes-support/vim/vim_8.1.1017.bb
rename to meta/recipes-support/vim/vim_8.1.1097.bb
index 7627d2844b..4de1bc3807 100644
--- a/meta/recipes-support/vim/vim_8.1.1017.bb
+++ b/meta/recipes-support/vim/vim_8.1.1097.bb
@@ -13,7 +13,7 @@ SRC_URI = "git://github.com/vim/vim.git \
file://vim-add-knob-whether-elf.h-are-checked.patch;patchdir=.. \
file://0001-src-Makefile-improve-reproducibility.patch;patchdir=.. \
"
-SRCREV = "493fbe4abee660d30b4f2aef87b754b0a720213c"
+SRCREV = "4fc8e2f8bb3eb42df0f72cfcc1f8f8e567e7ce4f"
S = "${WORKDIR}/git/src"
--
2.17.1
^ permalink raw reply related [flat|nested] 7+ messages in thread* Re: [PATCH v2] vim: update to 8.1.1097 2019-03-31 15:50 [PATCH v2] vim: update to 8.1.1097 Oleksandr Kravchuk @ 2019-03-31 20:11 ` Tom Rini 2019-03-31 20:19 ` Alexander Kanavin 0 siblings, 1 reply; 7+ messages in thread From: Tom Rini @ 2019-03-31 20:11 UTC (permalink / raw) To: Oleksandr Kravchuk; +Cc: openembedded-core [-- Attachment #1: Type: text/plain, Size: 1759 bytes --] On Sun, Mar 31, 2019 at 05:50:12PM +0200, Oleksandr Kravchuk wrote: > Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> > --- > .../vim/{vim-tiny_8.1.1017.bb => vim-tiny_8.1.1097.bb} | 0 > meta/recipes-support/vim/{vim_8.1.1017.bb => vim_8.1.1097.bb} | 2 +- > 2 files changed, 1 insertion(+), 1 deletion(-) > rename meta/recipes-support/vim/{vim-tiny_8.1.1017.bb => vim-tiny_8.1.1097.bb} (100%) > rename meta/recipes-support/vim/{vim_8.1.1017.bb => vim_8.1.1097.bb} (98%) > > diff --git a/meta/recipes-support/vim/vim-tiny_8.1.1017.bb b/meta/recipes-support/vim/vim-tiny_8.1.1097.bb > similarity index 100% > rename from meta/recipes-support/vim/vim-tiny_8.1.1017.bb > rename to meta/recipes-support/vim/vim-tiny_8.1.1097.bb > diff --git a/meta/recipes-support/vim/vim_8.1.1017.bb b/meta/recipes-support/vim/vim_8.1.1097.bb > similarity index 98% > rename from meta/recipes-support/vim/vim_8.1.1017.bb > rename to meta/recipes-support/vim/vim_8.1.1097.bb > index 7627d2844b..4de1bc3807 100644 > --- a/meta/recipes-support/vim/vim_8.1.1017.bb > +++ b/meta/recipes-support/vim/vim_8.1.1097.bb > @@ -13,7 +13,7 @@ SRC_URI = "git://github.com/vim/vim.git \ > file://vim-add-knob-whether-elf.h-are-checked.patch;patchdir=.. \ > file://0001-src-Makefile-improve-reproducibility.patch;patchdir=.. \ > " > -SRCREV = "493fbe4abee660d30b4f2aef87b754b0a720213c" > +SRCREV = "4fc8e2f8bb3eb42df0f72cfcc1f8f8e567e7ce4f" > > S = "${WORKDIR}/git/src" Looks better, thanks. Is there a particular fix / change you're doing this for? I ask since every commit is a version bump we might want to set a guideline of once a month or so for bumping vim to the latest. -- Tom [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2] vim: update to 8.1.1097 2019-03-31 20:11 ` Tom Rini @ 2019-03-31 20:19 ` Alexander Kanavin 2019-03-31 20:56 ` Tom Rini 0 siblings, 1 reply; 7+ messages in thread From: Alexander Kanavin @ 2019-03-31 20:19 UTC (permalink / raw) To: Tom Rini; +Cc: OE-core, Oleksandr Kravchuk On Sun, 31 Mar 2019 at 22:12, Tom Rini <trini@konsulko.com> wrote: > Looks better, thanks. Is there a particular fix / change you're doing > this for? I ask since every commit is a version bump we might want to > set a guideline of once a month or so for bumping vim to the latest. It's a bit insane upstream is doing that. Should we set PV to something like PV = "8.1+git${SRCPV}"? That way devtool/AUH/RRS will not be reporting a new version for each commit, and will only do that when 8.2 is out. Alex ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2] vim: update to 8.1.1097 2019-03-31 20:19 ` Alexander Kanavin @ 2019-03-31 20:56 ` Tom Rini 2019-03-31 22:28 ` Paul Barker 0 siblings, 1 reply; 7+ messages in thread From: Tom Rini @ 2019-03-31 20:56 UTC (permalink / raw) To: Alexander Kanavin; +Cc: OE-core, Oleksandr Kravchuk [-- Attachment #1: Type: text/plain, Size: 903 bytes --] On Sun, Mar 31, 2019 at 10:19:51PM +0200, Alexander Kanavin wrote: > On Sun, 31 Mar 2019 at 22:12, Tom Rini <trini@konsulko.com> wrote: > > Looks better, thanks. Is there a particular fix / change you're doing > > this for? I ask since every commit is a version bump we might want to > > set a guideline of once a month or so for bumping vim to the latest. > > It's a bit insane upstream is doing that. > Should we set PV to something like PV = "8.1+git${SRCPV}"? That way > devtool/AUH/RRS will not be reporting a new version for each commit, > and will only do that when 8.2 is out. No, we should follow what upstream does for version numbers, it's what other distros do. And on the related topic of "is it a stable branch?", it does seem like yes, it is. We should just remember to not update it more often than say the first of the month, without a specific reason. -- Tom [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2] vim: update to 8.1.1097 2019-03-31 20:56 ` Tom Rini @ 2019-03-31 22:28 ` Paul Barker 2019-03-31 22:31 ` Tom Rini 0 siblings, 1 reply; 7+ messages in thread From: Paul Barker @ 2019-03-31 22:28 UTC (permalink / raw) To: Tom Rini, Alexander Kanavin; +Cc: Oleksandr Kravchuk, OE Core On Sun, 31 Mar 2019, at 21:56, Tom Rini wrote: > On Sun, Mar 31, 2019 at 10:19:51PM +0200, Alexander Kanavin wrote: > > On Sun, 31 Mar 2019 at 22:12, Tom Rini <trini@konsulko.com> wrote: > > > Looks better, thanks. Is there a particular fix / change you're doing > > > this for? I ask since every commit is a version bump we might want to > > > set a guideline of once a month or so for bumping vim to the latest. > > > > It's a bit insane upstream is doing that. > > Should we set PV to something like PV = "8.1+git${SRCPV}"? That way > > devtool/AUH/RRS will not be reporting a new version for each commit, > > and will only do that when 8.2 is out. > > No, we should follow what upstream does for version numbers, it's what > other distros do. And on the related topic of "is it a stable branch?", > it does seem like yes, it is. We should just remember to not update it > more often than say the first of the month, without a specific reason. When I've done vim updates in the past I aimed for once every 3 months. I also looked at Debian/Fedora/etc to find a version that someone else has already tested in a distribution - with vim having so many "releases" you have the same issue you'd get from picking a random commit off the master branch from another project. Matching against a version used somewhere else gives us something to compare to when we hit a bug. Thanks, -- Paul Barker Managing Director & Principal Engineer Beta Five Ltd ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2] vim: update to 8.1.1097 2019-03-31 22:28 ` Paul Barker @ 2019-03-31 22:31 ` Tom Rini 2019-04-01 0:14 ` Oleksandr Kravchuk 0 siblings, 1 reply; 7+ messages in thread From: Tom Rini @ 2019-03-31 22:31 UTC (permalink / raw) To: Paul Barker; +Cc: Oleksandr Kravchuk, OE Core [-- Attachment #1: Type: text/plain, Size: 1668 bytes --] On Sun, Mar 31, 2019 at 06:28:31PM -0400, Paul Barker wrote: > On Sun, 31 Mar 2019, at 21:56, Tom Rini wrote: > > On Sun, Mar 31, 2019 at 10:19:51PM +0200, Alexander Kanavin wrote: > > > On Sun, 31 Mar 2019 at 22:12, Tom Rini <trini@konsulko.com> wrote: > > > > Looks better, thanks. Is there a particular fix / change you're doing > > > > this for? I ask since every commit is a version bump we might want to > > > > set a guideline of once a month or so for bumping vim to the latest. > > > > > > It's a bit insane upstream is doing that. > > > Should we set PV to something like PV = "8.1+git${SRCPV}"? That way > > > devtool/AUH/RRS will not be reporting a new version for each commit, > > > and will only do that when 8.2 is out. > > > > No, we should follow what upstream does for version numbers, it's what > > other distros do. And on the related topic of "is it a stable branch?", > > it does seem like yes, it is. We should just remember to not update it > > more often than say the first of the month, without a specific reason. > > When I've done vim updates in the past I aimed for once every 3 > months. I also looked at Debian/Fedora/etc to find a version that > someone else has already tested in a distribution - with vim having so > many "releases" you have the same issue you'd get from picking a > random commit off the master branch from another project. Matching > against a version used somewhere else gives us something to compare to > when we hit a bug. That's also a good idea, yes. My only concern is finding something moving forward otherwise quickly enough, but Fedora might do well for that. -- Tom [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2] vim: update to 8.1.1097 2019-03-31 22:31 ` Tom Rini @ 2019-04-01 0:14 ` Oleksandr Kravchuk 0 siblings, 0 replies; 7+ messages in thread From: Oleksandr Kravchuk @ 2019-04-01 0:14 UTC (permalink / raw) To: Tom Rini, Paul Barker; +Cc: OE Core On 01/04/2019 00:31, Tom Rini wrote: > On Sun, Mar 31, 2019 at 06:28:31PM -0400, Paul Barker wrote: >> On Sun, 31 Mar 2019, at 21:56, Tom Rini wrote: >>> On Sun, Mar 31, 2019 at 10:19:51PM +0200, Alexander Kanavin wrote: >>>> On Sun, 31 Mar 2019 at 22:12, Tom Rini <trini@konsulko.com> wrote: >>>>> Looks better, thanks. Is there a particular fix / change you're doing >>>>> this for? I ask since every commit is a version bump we might want to >>>>> set a guideline of once a month or so for bumping vim to the latest. >>>> It's a bit insane upstream is doing that. >>>> Should we set PV to something like PV = "8.1+git${SRCPV}"? That way >>>> devtool/AUH/RRS will not be reporting a new version for each commit, >>>> and will only do that when 8.2 is out. >>> No, we should follow what upstream does for version numbers, it's what >>> other distros do. And on the related topic of "is it a stable branch?", >>> it does seem like yes, it is. We should just remember to not update it >>> more often than say the first of the month, without a specific reason. >> When I've done vim updates in the past I aimed for once every 3 >> months. I also looked at Debian/Fedora/etc to find a version that >> someone else has already tested in a distribution - with vim having so >> many "releases" you have the same issue you'd get from picking a >> random commit off the master branch from another project. Matching >> against a version used somewhere else gives us something to compare to >> when we hit a bug. > That's also a good idea, yes. My only concern is finding something > moving forward otherwise quickly enough, but Fedora might do well for > that. I think it is indeed a good idea for maintainers to look up for stable projects, e.g Debian. It would be nice to have those guidelines set and clear though. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-04-01 0:14 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-03-31 15:50 [PATCH v2] vim: update to 8.1.1097 Oleksandr Kravchuk 2019-03-31 20:11 ` Tom Rini 2019-03-31 20:19 ` Alexander Kanavin 2019-03-31 20:56 ` Tom Rini 2019-03-31 22:28 ` Paul Barker 2019-03-31 22:31 ` Tom Rini 2019-04-01 0:14 ` Oleksandr Kravchuk
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.