Summary: | vim eclass tells user to enable bash completion for vim-core rather than xxd | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bo Ørsted Andresen (RETIRED) <zlin> |
Component: | Eclasses | Assignee: | Vim Maintainers <vim> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | CC: | halcy0n |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | # emerge -va1 vim-core |
Description
Bo Ørsted Andresen (RETIRED)
![]() Just to make it entirely clear: # eselect bashcomp enable vim-core !!! Error: /usr/share/bash-completion/vim-core doesn't exist # eselect bashcomp enable xxd # eselect bashcomp list Available completions: [1] xxd * When merging 6.4 like you said: * To enable command-line completion for vim-core, run: * * eselect bashcomp enable xxd Could you check it again please? I'm not seeing why it would do what you are getting at first glance. Created attachment 95455 [details]
# emerge -va1 vim-core
Btw. that really should be an elog rather than an einfo. # cat /var/log/portage/elog/app-editors\:vim-core-6.4\:20060830-105927.log INFO: postinst To enable command-line completion for vim-core, run: eselect bashcomp enable vim-core I have a ~x86 laptop with portage-2.1.1_rc1-r1. On the same laptop I have an stable (x86) chroot with portage-2.1-r2. It turns out that this issue is occuring in the chroot for both of vim-core-{6.4,7.0.17} but it is not occuring outside of the chroot (using the same eclasses and ebuilds). Moreover upgrading to portage-2.1.1_rc1-r1 in the chroot resolves the issue. With portage-2.1-r2 it does install xxd correctly but only the postinst is wrong as shown above. So perhaps the issue is that BASH_COMPLETION_NAME is unset in postinst with that version of portage... If you have any questions please ask. Also the issue occurs when doing: # emerge --usepkg -va1 vim-core both in and out of the chroot. Hmm, I'm not able to reproduce this either. Try building it again from scratch instead of using binary packages, as those may be messing up the cache of the eclass. If you're still able to reproduce this, feel free to re-open this bug, but I can see no possible reason in the eclass that would cause this to happen for vim-core... |