On Thu, Oct 04, 2007 at 02:06:12PM -0400, seth vidal wrote: > > On Thu, 2007-10-04 at 13:00 -0500, Clark Williams wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > seth vidal wrote: > > > On Thu, 2007-10-04 at 12:40 -0500, Clark Williams wrote: > > >> -----BEGIN PGP SIGNED MESSAGE----- > > >> Hash: SHA1 > > >> > > > Is it time to start writing simple, custom yum-utils just for mock? So > > > it can call them as a program but also so mock can more rigidly control > > > its output? > > > > > > > Maybe.... > > > > Are you talking about stuff that is a part of mock, a part of yum, or a > > separate > > package altogether? > > part of mock.
I agree. More of a long-term thing, though. Here is my list of stuff we need to work on: 1) "inside-out" setuid scheme (part of an overall revamp on how we see security for mock running. We currently dont have a coherent strategy or vision). 2) use yum-utils rather than calling cmdline 3) better caching (downloaded yum stuff, chroot cache) 4) more reliable mount/umount 5) Speedup options: ccache/distcc -- Michael -- Fedora-buildsys-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
