New version of mock working (I think)

Clark Williams williams at redhat.com
Mon Jun 26 21:50:03 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael_E_Brown at Dell.com wrote:
>> -----Original Message-----
>> From: fedora-buildsys-list-bounces at redhat.com
>> [mailto:fedora-buildsys-list-bounces at redhat.com] On Behalf Of
>> Clark Williams
>> Sent: Monday, June 26, 2006 4:07 PM
>> To: Discussion of Fedora build system
>> Subject: Re: New version of mock working (I think)
>>
>> Ok, I can go with that. Probably the most convincing portion
>> of the above argument is the idea of implementing a
>> root-privilege server as opposed to pushing that back to the
>> build system maintainers.
>>
>> So I suppose it means that we should publish a call-out
>> specification that says: if you invoke mock with the 
>> --server-mumble=X on the command line, mock will use X as a
>> URL to make an XML-RPC call with the state  as an argument in
>> <as yet to be determined> form.  We will then have to wrap
>> that in a try/except and possibly some timeout logic to make
>> sure that if the other end isn't speaking our language, we
>> continue or fail in a controlled fashion.
>
> I have some stock timeout and exception handling code that we can cut
> and paste in. It adds another 5-10 lines of code, and should make the
> code robust against what you describe.
>
> First order of business would be to get Dan's opinion on the matter,
> then settle on an API. I can code this up, along with a test harness.
> --
> Michael
I have some changes to mock.py that go with the new launcher
philosophy that should probably go in at the same time. We probably
want to tag and branch before we go off in this new direction.

Shouldn't we do something like the following:

$ cd mock
$ cvs tag r0_6-branchpoint
$ cvs tag -r r0_6-branchpoint -b r0_6-branch

I believe that this creates a branchpoint, then creates a branchtag
and leaves our head alone. We could then go merrily on our way with
the new launcher and the XML-RPC stuff while leaving 0.6 safe and sound.

Clark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEoFaLHyuj/+TTEp0RAsReAJ9OKB2DUQpw8zsKletz+qOW7wlZ2QCg3DGY
GBHpYn6aEUOYp/Jy3i4SBSw=
=Wxt5
-----END PGP SIGNATURE-----




More information about the Fedora-buildsys-list mailing list