Is that normal??

Is that normal??

[Jone]

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
* 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?

Re: Is that normal??

[Ricardo Wurmus]

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

Re: Is that normal??

[Ricardo Wurmus]

Hi Jone,

> I don't fully understand Guix in this case:

I forgot to answer your question: yes, it is normal that there might be
more than one variant of a package on your system.

To remove those that are no longer needed by any other package in any of
your profile generations run “guix gc”.  You may want to delete unused
profile and system generations first, though.

-- 
Ricardo

Re: Is that normal??

[Jone]

Hardlinks! I hadn't thought of that :) Thanks.

> To remove those that are no longer needed by any other package in any of
> your profile generations run “guix gc”.  You may want to delete unused
> profile and system generations first, though.

Well, that's obvious. 'guix gc' is executed by cron, and before listing
above I specifically executed 'guix package --delete-generations && guix gc
--collect-garbage'. In other words, in the first case, the result is
already after all possible purges, usually I leave only the last generation
and do not store the previous ones.