[arch-general] Why no git --depth=1 option for makepkg?

Jonathon Fernyhough jonathon at manjaro.org
Sat Mar 3 17:50:57 UTC 2018


On 03/03/18 08:48, mike lojkovic via arch-general wrote:
> It would be extremely nice to have shallow clone support for some packages.
> The Unreal git repo requires pulling down 20 gigabytes for a build, taking
> maybe a half hour each time.
> 

An effective workaround is to create a shallow clone prior to running
makepkg,

$ cd $SRCDEST
$ git clone --bare --depth=1 https://github.com/cisco/ChezScheme.git
ChezScheme
$ cd ChezScheme
$ git config remote.origin.fetch "+refs/*:refs/*"

and away you go.

However.

You can't just use --depth=1 on everything without running into "weird"
problems. For example, any VCS package that relies on tags for its
pkgver will fail to find the last tagged commit, and so the fetch depth
must be increased to extend to the tagged commit.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20180303/a11d8db8/attachment.asc>


More information about the arch-general mailing list