unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: carl hansen <carlhansen1234@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Fwd: warning: collision encountered
Date: Fri, 29 Jan 2016 08:25:09 +0100	[thread overview]
Message-ID: <87k2mskfu2.fsf@elephly.net> (raw)
In-Reply-To: <CAHEkXCQdhawp-6rV9=M-AUh_rK85Z1XMQ0H5RmzSV1sdMWhLGA@mail.gmail.com>


carl hansen <carlhansen1234@gmail.com> writes:

> 2354 packages in profile

What command did you use to install 2354 packages into your personal
profile?  Why would you install 2354 packages in your profile?

There are packages that provide files of the same name; for example
“samtools-0.1” and “samtools” both provide “$out/bin/samtools”.  When
they are both installed in the same profile, there is an obvious
collision.  People don’t install both these packages into the same
profile, because there is no way to disambiguate the colliding files.
Instead they will install them into *different* profiles using something
like

    guix package -p /path/to/profile -i samtools

If you feel the need to install all available packages into your profile
you’re doing it wrong.  Each package has its own directory in
“/gnu/store”, but profiles are the union of the files of each of the
directories of selected packages; at this point collisions may arise.

To resolve serious collisions remove one or the other package from your
profile.  Install it in a separate profile instead.

~~ Ricardo

      parent reply	other threads:[~2016-01-29  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHEkXCQCi=TxZGDfDJMoaFcjVFmueKd9pr1CPhCvVfim-kiJOA@mail.gmail.com>
2016-01-29  1:24 ` Fwd: warning: collision encountered carl hansen
2016-01-29  3:44   ` Leo Famulari
2016-01-29  5:46     ` carl hansen
2016-01-29  6:22       ` carl hansen
2016-01-29  8:09         ` Leo Famulari
2016-01-29  7:42       ` Leo Famulari
2016-01-29  7:25   ` Ricardo Wurmus [this message]

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=87k2mskfu2.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=carlhansen1234@gmail.com \
    --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).