On Sun, 2006-09-03 at 16:32 -0500, Clark Williams wrote:
Jeremy Katz wrote:
> Kind of an aside...
> On Sat, 2006-09-02 at 13:38 -0500, Clark Williams wrote:
>> Well, because in 0.7 and greater, there is no mockhelper. The
>> /usr/bin/mock program is a setuid root launcher that starts "python
>> /usr/bin/mock.py" with whatever arguments were passed in.
> It might be worth moving /usr/bin/mock.py to be somewhere that's not in
> the path... otherwise, this is bound to be somewhat confusing
>  To me, if to no one else :-)
Ah, it's all about you, Jeremy :)
As often as I can arrange :-P
I had considered it but was more concerned with other things (like
trying to clean up the BZ's for 0.6).
Where would you suggest? /opt/mock?
Nah, just that /usr/bin/mock should probably execute
perhaps /usr/libexec/mock.py -- that way, you don't do
and get hits for both mock and mock.py and become confused as to which
you're actually supposed to use