by aplund » Thu Oct 23, 2014 11:00 pm
$this->bbcode_second_pass_quote('WarheadsSE', 'T')hen there is also the fact of a full git tree checkout vs the ability for hosts like github to generate a tarball of a checkout at the given commit hash, reducing load on the automation greatly. (and is cachable)
But this is exactly what I don't understand. Pacman 4.1 will checkout into $SRCDIR and do a local clone from there. After the first checkout, only the most recent objects get pulled. This also works with a chroot build as $SRCDIR is bind mounted into the chroot.
So the load difference is that between doing a local checkout and unzipping/untaring a file. And more bandwidth is required if the source needs to be updated as the whole tarball has to be downloaded.
I can check the difference between unpacking the tarball and a local checkout as this may be many orders of magnitude different. I'm not sure.
However, I can see that if disk space is an issue, having a local copy of the git objects would take more space than desired.
But I think my original question stands. Why not use the new features in pacman 4.1? I'm not making a judgement, just asking. If the right way to do this is to pull github tarballs, then that's what I'll do. But I'd like to know why this is the right way.