-----Original Message----- From: fedora-buildsys-list-bounces@redhat.com [mailto:fedora-buildsys-list-bounces@redhat.com] On Behalf Of Jeremy Katz Sent: Sunday, September 03, 2006 5:12 PM To: Discussion of Fedora build system Subject: Re: Mock going forward
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[1]
Jeremy
[1] 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 moc<tab><tab> and get hits for both mock and mock.py and become confused as to which you're actually supposed to use
/opt/ is reserved for sysadmin installation of add-on packages and iirc is normally empty on a clean install. /usr/libexec/mock/mock.py sounds like a good choice. The other option is to do similar to how yum does it: /usr/share/mock-cli/mock.py. -- Michael
Jeremy
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list