Looks like a problem with the --global flag only % sudo eselect bashcomp enable --global eselect !!! Error: /usr/share/bash-completion/eselect doesn't exist % ls -l /usr/share/bash-completion/completions/eselect -rw-r--r-- 1 root root 1536 Nov 26 16:59 /usr/share/bash-completion/completions/eselect
Well, that is a problem with sudo not passing the env var, ES_BASHCOMP_DIRS
Just to make sure, what does "eselect bashcomp version" output?
Probably better if all issues related to the new bash-completion (and transition to it) are in one hand, so I've passed maintainership of app-admin/eselect-bashcomp to mgorny.
(In reply to Ulrich Müller from comment #2) > Just to make sure, what does "eselect bashcomp version" output? % eselect bashcomp version bashcomp.eselect 1.3.6 eselect 1.4.3
So somewhere along the lines bash-completion got "!app-eselect/eselect-bashcomp" in its RDEPEND. However, that means that there no longer is any /etc/bash/bashrc.d/bashcomp.sh installed. That means that app-eselect/eselect-bashcomp needs to be installing it, or something similar to it, to get bash completion working again.
(In reply to Tanktalus from comment #5) > So somewhere along the lines bash-completion got > "!app-eselect/eselect-bashcomp" in its RDEPEND. However, that means that > there no longer is any /etc/bash/bashrc.d/bashcomp.sh installed. That means > that app-eselect/eselect-bashcomp needs to be installing it, or something > similar to it, to get bash completion working again. app-shells/bash-completion (/etc/bash/bashrc.d/bash_completion.sh)
All current versions of bash-completion block split eselect-bashcomp, and it's masked for removal now.
