[gentoo-dev] bash-completion-2.1-r1

[Michał Górny]

Hello, all.

I'd like to ask finally: who feels himself responsible for deploying
bashcomp-2.1-r1? Does he have any kind of plan? Does anyone care at
all?

Do I have to say it's pretty far from professional to commit it
half-working, with no clear information how to proceed, neither for
users nor for developers? As far as I can see, there were mostly either
random patches or random bugs, with no clear generic guidelines.

I have enough projects on my back but I guess I'll end up carrying this
mess if nobody bothers to do so.


For future reference, I so far know the following:

1. bash supports two directories for completions: completionsdir
(/usr/.../completions) and compatdir (/etc). gentoo added a third
directory that i will call gentoodir (/usr/.../bash-completion).

2. bash sources all files in compatdir (at start?).

3. eselect used to symlink stuff from $gentoodir to $compatdir to
enable completions. therefore, all enabled stuff polluted
the environment all the time.

4. files in completionsdir are sourced when command matching filename
is typed in. that is 'foo <tab>' -> "$completionsdir/foo" is sourced.

5. in order for completionsdir to work,
/usr/share/bash-completion/bash_completion must be sourced first.
(is this just me? is this something to be done in global bashrc?)


Aside to the above, what needs to be answered:

1. how to properly disable completions the 'new way'?

2. do we want to support adding stuff to $compatdir? what do we do with
completions that don't fit $completionsdir?

3. how do we handle completion 'dependencies'? the 'old way' just
relied on them being sourced from $compatdir early. do we source them
explicitly now? do we put them in $compatdir unconditionally?

4. do we want to maintain eselect for bash completions? do we want it
to handle disabling and 'enabling' completions the 'new way'?

-- 
Best regards,
Michał Górny