Re: [gentoo-dev] Time to remove app-shells/bash-completion-config

[Jeremy Olexa]

On Tue, Feb 17, 2009 at 1:49 PM, Donnie Berkholz <dberkholz@g.o> wrote:
> On 11:55 Tue 17 Feb     , Jeremy Olexa wrote:
>> We should only be using eselect now to enable bash-completion. I think
>> bash-completion-config is broken now anyway
>> (https://bugs.gentoo.org/show_bug.cgi?id=253878). So, after this
>> change, I will p.mask b-c-c for removal.
>>
>> Any concerns? The upgrade path in the future is going to be wierd as
>> upstream is releasing v1.0 soon, but that is not concern for now.
>
> http://bugs.gentoo.org/show_bug.cgi?id=218557
>
> [Comment #0] mescalinum@g.o : 2008-04-20 12:26:38 0000
> -------------------------------------------------------------------------------
> if I type:
>
>  eselect bashcomp enable [TAB]
>
> I get a 'Killed' string printed to terminal:
>
>  eselect bashcomp enable Killed
>
> and it messes up the bash shell (i.e. history doesn't work anymore)
>
> [Comment #3] w.schwiedop@×××.de : 2008-07-31 00:41:39 0000
> -------------------------------------------------------------------------------
> Created an attachment (id=161784)
> Replacement for the current eselect completion script

This is not a fault of bash-completion but rather the eselect
bash-completion module itself. Since our eselect team is defunct, I
will mask the bash-completion USE flag for app-admin/eselect unless
someone steps up to take care of it (working patches exist, anyone?).
Analogy: If subversion's bash-completion module was broken, it
wouldn't block anything to do with app-shells/bash-completion. Instead
you would work it out with upstream.

Also: *enabling* bash-completion modules via eselect works just fine.
So, I don't get why this reply was needed on this thread.

-Jeremy