Re: git-fetch origin output is read-only - and reproducibility

[Robert Vollmert <rob@vllmrt.net>]

> On 29. Jul 2019, at 17:49, Ricardo Wurmus <rekado@elephly.net> wrote:
>> currently, when using the git-fetch origin, the resulting source will have
>> all files read-only.  Further phases trying to do reproducibility patches have
>> to manually chmod in order to be able to patch.
>> 
>> Can we change that?  For example change what this origin does or change what
>> the build systems do by default?
> 
> I think this would be good.  It’s a little annoying when switching from
> a tarball to git-fetch because you’ll have to add a phase that makes all
> files writable.
> 
> This would probably have to be changed in the unpack phase of the
> gnu-build-system, which copies files recursively when the sources are a
> directory (instead of a tarball).

At the risk of getting slightly off-topic, I was very surprised when I figured
out that such things were left to the build system. Couldn’t the source/origin
abstraction consistently refer a directory tree *or* a tarball?

Cheers
Robert