From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: A few questions about packages
Date: Tue, 13 Mar 2018 18:24:51 +0100 [thread overview]
Message-ID: <20180313182451.274ce27d@alma-ubu> (raw)
In-Reply-To: <20180313221535.5ddd956e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
On Tue, 13 Mar 2018 22:15:35 +0300
Jone <yeger9@gmail.com> wrote:
> I wrote a simple script:
>
> TRGT="*-gtk+-2.2*"
> for i in $(ls -d /gnu/store/$TRGT/)
> do
> echo
> echo "----------> $i"
> echo "$(guix gc --referrers $i | grep -v \.drv)"
> done
>
> Part of output:
> ----------> /gnu/store/595ydgdnkj9vdxr88dkscb0ws9rgjv0g-gtk+-2.24.31/
> /gnu/store/595ydgdnkj9vdxr88dkscb0ws9rgjv0g-gtk+-2.24.31
> /gnu/store/6h7w5z60zqx6802qxd98wcmx1yrhnzy5-xfce4-appfinder-4.12.0
> /gnu/store/8vy4gnmb17xc3hiqjd1b5z28vfsn8jzq-gtk-im-modules
> /gnu/store/fi77qxlq9ga6rgl9gg1xfxkfw7vps2l3-gtk-im-modules
> /gnu/store/ggrwghpwyfwrmxb90aj846c3ydwprqvl-gtk-im-modules
> /gnu/store/miiv6rnlrhbjk34l1ga7v6ys1x6983q4-libxfce4ui-4.12.0
> /gnu/store/rki1c8z0v7crppym7qzqys894pikxljc-garcon-0.4.0
[..]
> ----------> /gnu/store/rbzlcg13vpabvj2sr6c67icd15wq0vhz-gtk+-2.24.31/
> /gnu/store/16rwx833av4k48hk2diqj87mwsc457j3-gtk-im-modules
> /gnu/store/rbzlcg13vpabvj2sr6c67icd15wq0vhz-gtk+-2.24.31
>
>
> It is possible to draw a conclusion, that each application refers the
> SEPARATE version of library. What??? Somebody can explain it?
I also have a lot of those in my store, although I rarely do a guix gc.
Suppose you don't change anything on a packages definition, i.e.
leave name, version, depencencies, build-system etc. completely as they
were. If you then change anything on the dependencies of that package
(or its sub-dependencies) it will get rebuild (or re-downloaded) with
the same package-name and package-version but under a different
hash-sum.
That's the reason why there is the branch of "core-updates" packages
(see point 7 in [1]): Basicly every package in the distribution depends
on a core-updates package. If you change one of the core-updates, the
whole distribution needs to be rebuilt. Because this would cause much
compilation-work on users computers, core-updates will be collected and
compiled by Hydra on a separate branch. If everything is compiled and
under a certain level of errors, it will be merged back into master and
will be available via guix pull.
In your case it could be that you have installed the different library
instances via different guix pulls.
Björn
[1]
https://www.gnu.org/software/guix/manual/guix.html#Submitting-Patches
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-03-13 17:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 16:09 A few questions about packages Jone
2018-03-07 17:01 ` Ricardo Wurmus
2018-03-07 17:38 ` Konrad Hinsen
2018-03-07 19:26 ` Jone
2018-03-07 20:15 ` Jone
2018-03-07 21:23 ` Ricardo Wurmus
2018-03-11 21:43 ` Jone
2018-03-11 20:59 ` Ricardo Wurmus
2018-03-12 1:41 ` Jone
2018-03-13 19:15 ` Jone
2018-03-13 17:24 ` Björn Höfling [this message]
2018-03-13 19:36 ` Jone
2018-03-13 17:25 ` Ricardo Wurmus
2018-03-13 22:32 ` Jone
2018-03-13 22:38 ` Adonay Felipe Nogueira
2018-03-13 17:35 ` Björn Höfling
2018-03-13 22:48 ` Jone
2018-03-13 20:25 ` Björn Höfling
2018-03-10 11:26 ` Jone
2018-03-10 21:38 ` 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
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=20180313182451.274ce27d@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--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).