Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)
 

On 10/27/2009 12:24 AM, Brian Schueler wrote:
> The source package (with the patch included) can be found on the
> Beuth repo at:
> http://141.64.26.2/repo/bs/el5/SRPMS/mock-0.6.13-5.bs.el5.src.rpm

if you post just the patch against the mock src.rpm, we can include that
and get a testing package into c5-testing.

I can see there is quite a lot of use for this on some platforms. But I
quite like the fact that having zero state residue between builds is a
high value point for mock at the moment.

- KB
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)
 

Brian Schueler wrote:
> The patch is 'mock-cp_al.patch' and applies to mock-0.6.13.

The problem with linking files inside the chroot with files in a "base"
copy is there are a few programs that will modify a file directly. If
this happens you will modify the "base" file and taint your original copy.

-Shad
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)
 

On 10/28/2009 02:26 PM, Brian Schueler wrote:
> The patch is 'mock-cp_al.patch' and applies to mock-0.6.13.

I'll look into this and get some testing pkgs up.

- KB
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)
 

Brian Schueler wrote:
> Therefore is the second copy named 'clean-cache-copy', which
> repairs the tainted files. The clean-cache-copy is _not_ linked
> and represent the original root cache. rsync syncs it to the
> 'linked-cache-copy' and ensures that the content is always the
> same before each mock build.

And do all mock builds link against this copy? What happens if you have
3-4 builds going on at the same time? Are there any files that would be
linked between chroots? (If all the chroots link to linked-cache-copy
then the answer would be yes)

If you are just making a copy for each chroot then that isn't really any
different then just modifying existing behavior but removing the gzip on
the tarball

-Shad
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel