From: Ricardo Wurmus <rekado@elephly.net>
To: help-guix@gnu.org
Subject: Re: Is that normal??
Date: Sun, 20 Oct 2019 12:36:51 +0200 [thread overview]
Message-ID: <87mudvk8jg.fsf@elephly.net> (raw)
In-Reply-To: <CAH6o9V9hKj2tNcfen0X=iAeEyPRbSrjmecwtOJ5cGMns1SVDFg@mail.gmail.com>
Jone <yeger9@gmail.com> writes:
> Hi communiti!
> I don't fully understand Guix in this case:
>
> ❯ guix pull -l | grep Generation
> Generation 15 Sep 28 2019 17:10:57 (current)
> ❯ guix package -l | grep Generation
> Generation 155 Oct 20 2019 09:29:25 (current)
> ❯ ls -1d /gnu/store/*-gtk+-2.24.32/
> /gnu/store/0v0dwirkd5sixh91n0qby9jzjh8r6m6a-gtk+-2.24.32
> /gnu/store/25sxqwh2x0j04z59yk49nrliz61cwrhd-gtk+-2.24.32
> /gnu/store/386h8ljfhzlpwxjh1682pqh2gxzrxn08-gtk+-2.24.32
> /gnu/store/3z1f2phvbzzjlxr1gvmf5qjprfp5jb7k-gtk+-2.24.32
> /gnu/store/4sdyqsy2np503akvk182xr3510067zgz-gtk+-2.24.32
> /gnu/store/6yabql5aiwnkaqbsi7mvwqiahaswl5ai-gtk+-2.24.32
> /gnu/store/bfa9122w70civ5bz4985h1cli20p0q1b-gtk+-2.24.32
> /gnu/store/ia1vzawl48yqfyg6v2zfxv47kisj49cp-gtk+-2.24.32
> /gnu/store/nzncsbi6d58k7zqzsr4rxyn8inn8pjhm-gtk+-2.24.32
> /gnu/store/wlc89m9yrb65mjbgw0zkabynms0j0xqa-gtk+-2.24.32
A list like this is rarely enlightening, because it’s not clear where
they are needed (if at all).
> * with the same subfolders *gtk+-2.24.32/{bin,etc,include,lib,share}
> ** and some with the same size
>
> What about deduplication and why different hashes?
What about deduplication? Deduplication is done at the file level via
/gnu/store/.links. You can look at the number of links a file has to
see that this actually works:
$ stat --format=%h /gnu/store/3qjd4jfjhd8c8skwlakl677n1fhpmfsr-gtk+-2.24.32/share/doc/gtk+-2.24.32/COPYING
19
This means that the same COPYING file exists 19 times, but all these
files are hard links to the same single file. You can also get
(slightly less impressive) numbers for binaries:
$ stat --format=%h /gnu/store/3qjd4jfjhd8c8skwlakl677n1fhpmfsr-gtk+-2.24.32/bin/gtk-builder-convert
4
Why different hashes? Different inputs will always lead to different
hashes. Why different inputs? Well, either the input package itself
got changed directly, or it has a different hash due to a change in its
inputs.
--
Ricardo
next prev parent reply other threads:[~2019-10-20 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 13:05 Is that normal?? Jone
2019-10-20 10:36 ` Ricardo Wurmus [this message]
2019-10-20 10:39 ` Ricardo Wurmus
2019-10-20 14:23 ` Jone
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=87mudvk8jg.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@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.
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).