unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Mortimer Cladwell <mbcladwell@gmail.com>
Cc: zimoun <zimon.toutoune@gmail.com>, help-guix@gnu.org
Subject: Re: How to use guix hash --serializer?
Date: Tue, 04 Jan 2022 21:57:30 +0100	[thread overview]
Message-ID: <87bl0rus8o.fsf@nckx> (raw)
In-Reply-To: <CAOcxjM7sdKY24Fivt6wu=w0t1FxSNL-Pyfjo9=Eop7nZP9nGkA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

Martimer,

Mortimer Cladwell 写道:
> looks like the difference, other than make/git related files are 
> four empty
> directories doc, scripts, shinyln and tests, so appears empty 
> directories
> are not allowed?

They are allowed but they change the hash, just as any other 
difference would.

Missing or extraneous directories are no less meaningful than 
files or permissions, etc., and can easily cause the build to fail 
(‘cd: blah: No such file or directory’, ‘mkdir: cannot create foo: 
File exists’) or otherwise behave very differently.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-01-04 21:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 16:32 How to use guix hash --serializer? Mortimer Cladwell
2022-01-04 16:53 ` zimoun
2022-01-04 19:09   ` Timothy Sample
2022-01-04 19:48     ` Mortimer Cladwell
2022-01-04 19:57       ` Tobias Geerinckx-Rice
2022-01-04 19:58       ` Mortimer Cladwell
2022-01-04 20:17       ` zimoun
2022-01-04 20:44         ` Mortimer Cladwell
2022-01-04 20:57           ` Tobias Geerinckx-Rice [this message]
2022-01-04 21:02           ` zimoun
2022-01-04 21:16             ` Mortimer Cladwell
2022-01-04 20:54     ` zimoun
2022-01-05  1:44       ` Timothy Sample
2022-01-05  7:43         ` zimoun

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87bl0rus8o.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=mbcladwell@gmail.com \
    --cc=zimon.toutoune@gmail.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).