Summary: | app-eselect/eselect-vi-1.1.9: vis doesn't show up in 'eselect vi list' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Capricelli <orzel> |
Component: | Current packages | Assignee: | Vim Maintainers <vim> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | contact, eselect, jstein, proxy-maint, smp |
Priority: | Normal | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch to add vis to eselect-vi |
Description
Thomas Capricelli
2017-05-07 22:15:52 UTC
Not a problem of eselect proper, but of the vi module. Reassigning to its maintainer (namely, vim project). Despite not showing up in $ eselect vi list, you can still set the symlink: $ eselect vi list Available vi implementations: [1] vim [2] busybox $ eselect vi show Current vi implementation: vis Created attachment 616722 [details, diff]
patch to add vis to eselect-vi
This works, although you need to unmask ~amd64 because only eselect-vi-1.1.9-r1 is EAPI>5.
*** Bug 830821 has been marked as a duplicate of this bug. *** The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/eselect-vi.git/commit/?id=158d9b0828f55bf12ca409923f34f02901861c39 commit 158d9b0828f55bf12ca409923f34f02901861c39 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-11-22 00:27:42 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-22 00:30:57 +0000 Add support for vis Closes: https://bugs.gentoo.org/617774 Signed-off-by: Sam James <sam@gentoo.org> vi.eselect.in | 1 + 1 file changed, 1 insertion(+) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6de21c263da0be0c93387d708497b3f6324075d7 commit 6de21c263da0be0c93387d708497b3f6324075d7 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-11-22 00:33:13 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-22 01:04:40 +0000 app-eselect/eselect-vi: add 1.3 Closes: https://bugs.gentoo.org/617774 Signed-off-by: Sam James <sam@gentoo.org> app-eselect/eselect-vi/Manifest | 1 + app-eselect/eselect-vi/eselect-vi-1.3.ebuild | 21 +++++++++++++++++++++ 2 files changed, 22 insertions(+) I'm not sure to follow. The previous link is a commit to 'gentoo' git, but i can't see this eselect-vi/eselect-vi in my portage tree, even after syncing several days later. How can we check/validate ??? Try a different mirror. So what you say is that I should actually have eselect-vi-1.3 ? I do get a lot of updates.. As usual. I'm syncing using git. And indeed, there's no 1.3 here: https://github.com/gentoo-mirror/gentoo/tree/stable/app-eselect/eselect-vi The main page on github says the repository was updated 11min ago. 20221122 > 1.3 > 1.2, so upgrade to the 2022 version...? The git history will show you what happened: 1.3 was added, and then quickly replaced with 20221122. https://github.com/gentoo-mirror/gentoo/commits/stable/app-eselect/eselect-vi oh ? 20221122 looks like a git snapshot or whatever. It's ~amd64, i hadn't even noticed it.. unmasked and tested, i can confirm "eselect vi" now knows about vis. Thanks ! |