From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: 07/07: guix: python-build-system: Fix an outdated comment.
Date: Sun, 16 Oct 2016 00:16:27 +0200 [thread overview]
Message-ID: <87d1j1b6mc.fsf@gnu.org> (raw)
In-Reply-To: <20161013224529.1a55e84a@scratchpost.org> (Danny Milosavljevic's message of "Thu, 13 Oct 2016 22:45:29 +0200")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
>> Sorry, I didn't realize that altering comments here would have an
>> effect; I would have warned Hartmut if I had.
>
> Out of curiousity, why does it have an effect?
The file is imported in the build environment (chroot) of all the
packages that use ‘python-build-system’. It’s an input of the
derivation of those packages, so when it changes, all these derivations
change.
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
>> Sorry, I didn't realize that altering comments here would have an
>> effect; I would have warned Hartmut if I had.
>
> I'm sorry, too. I didn't expect that changing a comment would have any
> impact on building packages. Aren't the the files converted to some
> canonical form prior to deciding whether they changed?
No. There’s no “decision” as to whether they changed; instead, they
just happen to be part of the hash of the output file name.
That said, don’t be sorry gentlefolks: these things happen. ;-)
Ludo’.
next prev parent reply other threads:[~2016-10-15 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161013152324.1276.70078@vcs.savannah.gnu.org>
[not found] ` <20161013152324.EF9C7220170@vcs.savannah.gnu.org>
2016-10-13 19:32 ` 07/07: guix: python-build-system: Fix an outdated comment Mark H Weaver
2016-10-13 19:39 ` Leo Famulari
2016-10-13 20:45 ` Danny Milosavljevic
2016-10-15 22:16 ` Ludovic Courtès [this message]
2016-10-14 7:55 ` Hartmut Goebel
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=87d1j1b6mc.fsf@gnu.org \
--to=ludo@gnu.org \
--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.