I don't mind installing just one shell script unconditionally. But I think we should add a use flag to advertise it. I was about to make an ebuild to add bash-completion support for gsettings until I realized the build already installed it.
I am unsure about adding a USE flag for installing a single file (this reminds me the "logrotate" USE flag issue that was finally dropped due this). And adding a use flag to simply advertise it's being installed... looks overkill to me, but maybe any other team member can clarify this situation a bit :-/
Afaik, the bash-completion eclass adds the use flag only to make sure the user has bash-completion and eselect packages installed. This is imho overkill and it indeed meets the point that was made on the ml that installing one file that doesn't in itself depends on anything doesn't warrant a USE flag. Maybe the discussion should be brought to dev ML to make the situation clearer for bash-completion too.
The way we are installing bash-completion stuff in 2.30 mimics the new preferred way of handling bash-completion files as used by bash-completion-r1.eclass (that makes bash-completion.eclass deprecated)
