[Bash-completion-devel] Bits from the Bash-Completion Team
Steve Kemp
skx at debian.org
Tue May 6 19:40:26 UTC 2008
On Fri May 02, 2008 at 21:52:41 +0200, David Paleino wrote:
> A general rule for completion code: bash-completion has always integrated
> patches in its main code. What we (me and Luk) would like to achieve is to have
> completion provided by *single* *packages*, not by bash-completion (which would
> then be just a backend). Example: completion for mount and umount would go into
> the "mount" package, which would install the respective files
> into /etc/bash_completion.d/ .
I took this to mean that existing completion could be updated for
the moment - but that adding completion for whole new commands would
be a bad idea; and should happen in the package itself.
But I guess going forward we need to think about splitting up the
main file into a collection of small ones, so for example the ssh/scp
code would go into /etc/bash_completion.d/ as a first step, then
once we know that doesn't break we submit a bug report against
openssh-client to have them include the file.
Does that sound reasonable? (I guess the downside is timing; if
having lots of little files causes things to slow down too much, or
perhaps having to coordinate the package release such that we don't
have bash-completion + openssh-client both trying to own the same
file.)
I guess 360628 is relevant, as is the contents of the TODO file.
Steve
--
# The Debian Security Audit Project.
http://www.debian.org/security/audit
More information about the Bash-completion-devel
mailing list