[Bash-completion-devel] [bash-completion-Bugs][312795] Bash completion should also load files from /usr/local/etc/bash_completion.d

[bash-completion-bugs at alioth.debian.org]

Bugs item #312795, was changed at 2010-11-01 07:47 by Ville Skyttä 
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312795&group_id=100114

Status: Open
Priority: 3
Submitted By: Alexandre Quessy (alexandrequessy-guest)
Assigned to: Nobody (None)
Summary: Bash completion should also load files from /usr/local/etc/bash_completion.d 
Distribution: None
Originally reported in: None
Milestone: None
Status: None
Original bug number: 


Initial Comment:
Hello,

In which paths does the bash completion look? By looking at /etc/bash_completion, I think it's only /etc/bash_completion, not /usr/local/etc/bash_completion.d

That means that my Makefile.am should not install the bash completion file to $(sysconfdir)/bash_completion.d, but rather to /etc/bash_completion.d. (hard-coded)

Here is an example from my Toonloop project: 

completiondir = $(sysconfdir)/bash_completion.d
dist_completion_DATA = toonloop

That's slightly annoying, because installing from a tarball will override the file from the Debian package, if installed. 

It would be much nicer if the /etc/bash_completion would also look in the /usr/local/etc/bash_completion.d directory. 

Am I right?
Best regards,
Alexandre Quessy
http://wiki.debian.org/AlexandreQuessy 

----------------------------------------------------------------------

>Comment By: Ville Skyttä  (scop-guest)
Date: 2010-11-01 17:18

Message:
You're right, this is kind of a bug. We have a roadmap item for a possible new directory layout for the next release, so things will probably change. Until then, I can only suggest that you hardcode /etc/bash_completion.d as the completion dir instead of using $(sysconfdir)/bash_completion.d

It might not be a bad idea to add a pkgconfig *.pc file for bash completion that external completion authors could use to query the completion snippet path(s).

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312795&group_id=100114