After updating to bash-completion-2.1-r91 I get an error bash: /etc/profile.d/bash-completion.sh: No such file or directory during login. It seems that bash-completion.sh has been renamed to bash_completion.sh, with no transition symlink or a portage news entry. It doesn't block my log-in but I'm still rather surprise that this hits me in the face. Maybe we can make it a bit smoother. What do you think?
Agree with this comment. I spent almost one hour to figure out why my completion isn't working any more ... And i didn't get the error because my bashrc is write like that : [[ -f /etc/profile.d/bash-completion.sh ]] && . /etc/profile.d/bash-completion.sh A warning during the update could be a good thing ...
We'll probably be fixing this with another move, for bug #338335.
The initialization files have been moved to bashrc.d now, and therefore it shouldn't be necessary to source them anymore. Do you think we should add some more information about that?
(In reply to Michał Górny from comment #3) > The initialization files have been moved to bashrc.d now, and therefore it > shouldn't be necessary to source them anymore. I noticed the second move but updated the source line to say source /etc/bash/bashrc.d/bash_completion.sh So at least I did fail at understanding that that location resolves need for sourcing. > Do you think we should add > some more information about that? I tend to say yes but I guess I'm biased here.
(In reply to Sebastian Pipping from comment #4) > (In reply to Michał Górny from comment #3) > > The initialization files have been moved to bashrc.d now, and therefore it > > shouldn't be necessary to source them anymore. > > I noticed the second move but updated the source line to say > > source /etc/bash/bashrc.d/bash_completion.sh > > So at least I did fail at understanding that that location resolves need for > sourcing. > > > > Do you think we should add > > some more information about that? > > I tend to say yes but I guess I'm biased here. It's mentioned in the bash-completion news item RFC: | Lastly, we have solved the issue causing bash-completion support to be | enabled by default on login shells only. If you needed to explicitly | source 'bash_completion' script in bashrc, you can safely remove that | code now since system-wide bashrc takes care of loading it. I'll probably commit it soon and request stabilization of new bashcomp.
Alright, cool, I didn't know there was a news item in preparation. I'm all happy if there's a news item soon.
How's this coming along?
The news item was committed a long time ago, so closing.
