Attached is a bash_completion snippet for mock.  Let me know if you'd like me 
to commit this.

why not put this in the bash completion package? It just seems like an odd place
to put it in the mock package if only in that it IMPLIES a
requirement/Suggestion of bash-completion.

I originally had it in my local bash-completion package, but I'd rather have 
it in mock for a few reasons: 
- Two triggers (triggerin/triggerun) less in the bash-completion package 
- More likely to be kept up to date when mock itself is updated 
- More likely to contain the switches for the installed version of mock 

This seems like a slippery slope, though.

What keeps us from adding a bash completion file to EVERY cli package in extras
and core?

It just seems like a lot of clutter especially if you're not using bash completion.

Okay, so we disagree, let's not waste time arguing.  A simple yes/no will do, 
and I'll deal with it accordingly. 

okay,

no.

It seems like the wrong place to put it, that's all.

sorry.

Ok, thanks, I'll add it to bash-completion then. 
 
But I can't help wondering what do you think the various foo.d directories in 
a lot of apps are for, if not for the purpose of providing a place for other 
apps to drop their snippets in in order to integrate with something.