unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andy Tai <atai@atai.org>
Cc: 61864-done@debbugs.gnu.org
Subject: bug#61864: [PATCH] scripts: expose 'allow-collisions' for 'guix install'
Date: Sat, 1 Apr 2023 12:54:44 -0400	[thread overview]
Message-ID: <ZChh1GFQnKRBITmL@jasmine.lan> (raw)
In-Reply-To: <CAJsg1E9HFXCOjg4Q9sfYDH0eDR6ooXu1eseXpmb=wZXmRzNdvQ@mail.gmail.com>

On Thu, Mar 02, 2023 at 12:38:45PM -0800, Andy Tai wrote:
> I run into collisions in profile from time to time and I can resolve it via
> 
> guix package --allow-collosions -i (or -u)
> 
> so it is useful to make that available in the two "alias" commands as well

I see, that makes sense. Sorry I'm slow to reply, I thought about it for
a while.

Allowing profile collisions is a risky action that can cause subtle and
hard to diagnose bugs, and it often is done without understanding the
consequences. In my experience, collisions are often allowed by people
who don't understand the negative effects of collisions, or how profiles
are constructed.

When reported, the consequent problems can take up a lot of time for the
people trying to help.

Because of those reasons, I prefer to only expose this option in `guix
package`, which is a more advanced interface. My hope is that
segregating the option like this will discourage use of
'--allow-collisions' and prevent an increase in bug reports of the "user
error" type.

If you disagree, please feel free to reopen the bug and optionally CC
some other reviewers, or bring it up on IRC.




  reply	other threads:[~2023-04-01 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  6:28 [bug#61864] [PATCH] scripts: expose 'allow-collisions' for 'guix install' Andy Tai
2023-03-02 20:02 ` Leo Famulari
2023-03-02 20:38   ` Andy Tai
2023-04-01 16:54     ` Leo Famulari [this message]
2023-03-03  6:07 ` [bug#61864] [PATCH v2] scripts: Expose " Andy Tai

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=ZChh1GFQnKRBITmL@jasmine.lan \
    --to=leo@famulari.name \
    --cc=61864-done@debbugs.gnu.org \
    --cc=atai@atai.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).