all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: git-fetch origin output is read-only - and reproducibility
Date: Mon, 29 Jul 2019 17:49:48 +0200	[thread overview]
Message-ID: <87k1c07sdf.fsf@elephly.net> (raw)
In-Reply-To: <20190729165743.04e6a516@scratchpost.org>


Hi Danny,

> 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).

I don’t know if that’s safe to do.  Are other fetch methods affected as
well?  hg-fetch or svn-fetch, for example?

-- 
Ricardo

  reply	other threads:[~2019-07-29 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 14:57 git-fetch origin output is read-only - and reproducibility Danny Milosavljevic
2019-07-29 15:49 ` Ricardo Wurmus [this message]
2019-07-29 15:58   ` Robert Vollmert
2019-07-29 16:10     ` Ricardo Wurmus
2019-07-30  7:37       ` Robert Vollmert
2019-08-22 21:41         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1c07sdf.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.