[Bash-completion-devel] [bash-completion-Bugs][313601] bash-completion shouldn't provide completions for generic named tools

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

Bugs item #313601, was changed at 2012-04-08 13:27 by Igor Murzov
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313601&group_id=100114

Status: Open
Priority: 3
Submitted By: Vladimir Lomov (lomov_vl-guest)
Assigned to: Nobody (None)
Summary: bash-completion shouldn't provide completions for generic named tools 
Distribution: --Distribution-Agnostic--
Originally reported in: None
Milestone: None
>Status: Accepted
Original bug number: 


Initial Comment:
Hello,
currently bash-completion provides completion for tool `makepkg' assuming that it is Slackware one, but there is other tool with such name: in Archlinux the package manager, pacman, provides tool `makepkg' and completion for it, see
http://projects.archlinux.org/pacman.git/tree/contrib

I think bash-completion behaves wrongly, it shouldn't provide completion for `makepkg' it is purpose of the "package", in Slackware one would install necessary tool and the package should provide optionally the completion for bash, that's how package `pacman' do in Archlinux.




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

>Comment By: Igor Murzov (garik-guest)
Date: 2012-04-08 19:12

Message:
You are probably right. But it's would be hard to merge slackware-related completions into Slackware repositories. I have some rather old patches, that are still not merged in Slackware for unknown reasons, and I'm not sure that completions would be accepted. May be it's easier to remove conflicting completions from Arch's package?


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

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