| 1 |
On Tue, Jun 21, 2011 at 4:35 PM, <bugzilla-daemon@g.o> wrote: |
| 2 |
> --- Comment #2 from Gilles Dartiguelongue <eva@g.o> 2011-06-21 09:35:59 UTC --- |
| 3 |
> Afaik, the bash-completion eclass adds the use flag only to make sure the user |
| 4 |
> has bash-completion and eselect packages installed. This is imho overkill and |
| 5 |
> it indeed meets the point that was made on the ml that installing one file that |
| 6 |
> doesn't in itself depends on anything doesn't warrant a USE flag. Maybe the |
| 7 |
> discussion should be brought to dev ML to make the situation clearer for |
| 8 |
> bash-completion too. |
| 9 |
|
| 10 |
OK let's hear from the ML. Another good thing from bash-completion |
| 11 |
eclass is that it advertises bash-completion in pkg_postinst (though |
| 12 |
some packages miss this). If we're OK for dev-libs/glib not to use |
| 13 |
bash-completion use flag, what about the others, drop the use flag? |
| 14 |
|
| 15 |
BTW while I looked over to see how bash-completion use flag is used, I |
| 16 |
encountered some ebuilds that can use improvement. Will probably open |
| 17 |
another QA bug for these. |
| 18 |
|
| 19 |
- bash-completion_pkg_postinst is not called: dev-lang/R, |
| 20 |
dev-util/schroot, dev-vcs/git, dev-vcs/subversion, |
| 21 |
sci-visualiztion/epix, sys-apps/paludis, sys-cluster/drbd, |
| 22 |
sys-cluster/util-vserver, sys-power/nut |
| 23 |
|
| 24 |
- do not use dobashcompletion: app-misc/task, app-portage/udept, |
| 25 |
app-shells/autojump |
| 26 |
|
| 27 |
- do not use bash-completion eclass: app-pda/osynctool, |
| 28 |
x11-wm/awesome (automatically installed?) |
| 29 |
|
| 30 |
- die after dobashcompletion, or explicitly check for the use flag |
| 31 |
before calling: app-portage/flaggie, dev-vcs/topgit, net-misc/aria2, |
| 32 |
net-analyzer/linkchecker, www-apps/blazelogger |
| 33 |
-- |
| 34 |
Duy |
Archives