GNOME Bugzilla – Bug 697818
[PATCH] Add "shallow_clone" option
Last modified: 2013-05-15 13:59:04 UTC
This just maps to --depth=1 for git at the moment; I didn't bother with other version control systems because to be honest they're basically irrelevant. Using this option is a *lot* faster to just get an initial build going. gdk-pixbuf's git repo is an 100MB download, but only 1.8 currently with depth 1. --- jhbuild/config.py | 1 + jhbuild/versioncontrol/git.py | 10 ++++++---- 2 files changed, 7 insertions(+), 4 deletions(-)
Created attachment 241273 [details] [review] Add shallow clone option
Created attachment 241294 [details] [review] updated patch We also need to use the specified branch for the original checkout, which is an optimization when not using this option too.
Review of attachment 241294 [details] [review]: If i understood the code correctly, the 'shallow_clone' is not the default. If that is correct, ACK. ::: jhbuild/config.py @@ +60,3 @@ 'use_local_modulesets', 'ignore_suggests', 'modulesets_dir', 'mirror_policy', 'module_mirror_policy', 'dvcs_mirror_dir', + 'shallow_clone', why dedicate one line for this key only?
Fixed with unnecessary whitespace deleted.
Cool, please update the status of patch too next time :)
Seems that changeset 40b70d75563f783cf41c403e7c797ab683803c52 from jhbuild breaks jhbuild for me. When I try to build wayland, I get: $ jhbuild buildone wayland Traceback (most recent call last):
+ Trace 231918
jhbuild.main.main(sys.argv[1:])
config = jhbuild.config.Config(options.configfile)
self.load(filename)
setattr(self, name, config[name])
https://git.gnome.org/browse/jhbuild/commit/?id=c4ed9c53fc1d54dc76051a3a979dd0f8860991ad
I've just noticed this change. that's cool, I have a similar option for bazaar in my customized jhbuild. In Bazaar it is called lightweight checkout (option --light) . I'll make it use shallow_clone and send a patch soon.