On fre, 2016-03-18 at 18:43 +0100, Alexander Larsson wrote:
Does this make sense? Do you forsee any other problems with this approach?
I started experimenting with this, and have a script now that essentially does this. See the attached script. It relies on this patch-set for "pull --untrusted" support: https://bugzilla.gnome.org/show_bug.cgi?id=764125 It seems to work, including verifying the remote branch name via the summary signature. There are a fee nasty parts though: * We need to copy the remote config, because the remote configuration is not inherited from the parent repo. It looks to me like the code supported this once upon a time, but this has bit-rotted. Are you interested in re-instating this? * There is some magic knowledge about the repo format when the summary cache is copied to the summary file location. Kinda ugly, but works. 3) We have to create a temporary remote to pull in the final results into the real repo. It would be nice if we could pull from the "real" remote, but supply a custom url for that particular pull operation. Then we didn't have to do that. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl redhat com alexander larsson gmail com He's a time-tossed coffee-fuelled farmboy on the run. She's an artistic impetuous queen of the dead from a family of eight older brothers. They fight crime!
Attachment:
setup-repo.sh
Description: application/shellscript