From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Dealing with common collisions in profiles
Date: Thu, 10 Sep 2015 19:53:49 +0200 [thread overview]
Message-ID: <CAKrPhPMQYt2ZnoRdsexm7A-od2p0=xuuUXWwbqdPFc994wwLow@mail.gmail.com> (raw)
In-Reply-To: <87egi7qppi.fsf@gnu.org>
On Wed, Sep 9, 2015 at 10:53 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hello!
>
> You’ve probably noticed that as soon as there’s a non-negligible number
> of packages in a profile, there are collisions. It’s really harmless,
> but seriously annoying. Here’s a collection of those I get:
>
> share/glib-2.0/schemas/gschemas.compiled
> share/icons/hicolor/icon-theme.cache
> lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
> lib/perl5/5.16.1/x86_64-linux/perllocal.pod
>
> Federico, I know ‘glib-or-gtk-build-system’ builds the first 3 items on
> purpose, but what do you think can be done about them? At worst we
> could always change (guix build profiles) to not report collisions for
> those.
Hey Ludovic,
the first two are indeed generated by 'glib-or-gtk-build-system'. I
suppose we could add hooks to generate the caches at profile
generation time and remove the relative phases from the build system.
I'm not sure about the 3rd one, but probably the same approach would work.
Regards,
Fede
>
> The .pod files are used by ‘perldoc’ IIUC. What can be done about them?
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2015-09-10 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 20:53 Dealing with common collisions in profiles Ludovic Courtès
2015-09-10 17:53 ` Federico Beffa [this message]
2015-09-10 19:24 ` Ludovic Courtès
2015-09-17 14:22 ` Pjotr Prins
2015-09-18 19:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKrPhPMQYt2ZnoRdsexm7A-od2p0=xuuUXWwbqdPFc994wwLow@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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.