Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: bash-completion-2.1-r1
Date: Tue, 10 Sep 2013 00:19:23
Message-Id: pan$a9c90$10a0bf2c$4820258b$5770354f@cox.net
1 Michał Górny posted on Mon, 09 Sep 2013 17:18:50 +0200 as excerpted:
2
3 > Dnia 2013-09-09, o godz. 18:12:08 Nikos Chantziaras <realnc@×××××.com>
4 > napisał(a):
5 >
6 >> On 09/09/13 13:05, Michał Górny wrote:
7 >> >
8 >> > Trying plain:
9 >> >
10 >> > complete -r git
11 >> >
12 >> > it removes git completion indeed. But when I type 'git <tab>', it is
13 >> > loaded back :).
14 >>
15 >> You can disable the "bash-completion" USE flag of dev-vcs/git. This
16 >> isn't a real solution, of course, since you need to recompile the whole
17 >> package every time you want to disable or enable bash completion. But
18 >> if you don't intend to actually ever use Git's completion, then this
19 >> should work.
20 >
21 > And it is a bug since completions are supposed to be installed indep of
22 > USE flags.
23
24 Indeed. The general gentoo policy is that "trivial" files such as bash-
25 completions, systemd unit files, etc, aren't to be install-controlled via
26 USE flags, for exactly the reason given -- the cost of rebuilding the
27 entire package just to change one's mind is considered too high to pay
28 for the "trivial" amount of space taken by such files, particularly so
29 when people who /really/ care about it already have the install-mask
30 solution available.
31
32 However, that totally skirts another problem as well. If one user on a
33 system wants completion and another doesn't, installation-control isn't
34 going to cut it. That's a problem that per-user eselect bash-completion
35 USED to address, but doesn't with the new bash-completion.
36
37 --
38 Duncan - List replies preferred. No HTML msgs.
39 "Every nonfree program has a lord, a master --
40 and if you use the program, he is your master." Richard Stallman

Replies

Subject Author
[gentoo-dev] Re: bash-completion-2.1-r1 Martin Vaeth <vaeth@××××××××××××××××××××××××.de>