unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: bokr@bokr.com
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: 70215@debbugs.gnu.org
Subject: bug#70215: Documentation about uninstalling
Date: Thu, 11 Apr 2024 14:36:21 +0200	[thread overview]
Message-ID: <20240411123621.GA2976@LionPure> (raw)
In-Reply-To: <CAEtmmeyB6fc69ek_vxwdrCE0iv594_ARA-h4gj-OOF4YAH0wmQ@mail.gmail.com>

On +2024-04-11 02:08:35 +0200, Rostislav Svoboda wrote:
> Do you mean the guix-install.sh script? If so then what about the
> https://guix.gnu.org/manual/devel/en/guix.html#index-uninstallation_002c-of-Guix
> ?
> 
> 
> 
It says (a bit reformatted):
┌────────────────────────────────────────────────────────────┐
│ Should you eventually want to uninstall Guix, run the same │
│ script with the --uninstall flag:                          │
│                                                            │
│ ./guix-install.sh --uninstall                              │
│                                                            │
│ With --uninstall, the script irreversibly deletes all the  │
│ Guix files, configuration, and services.                   │
└────────────────────────────────────────────────────────────┘

My 2 cents' worth:

That sounds dangerous -- what about putting all the deletions
in a TAR_DICT/TAR_FILE_NAME.tgz as a default, with suitable
default alternative commands for various capitalized names
in a (bash) select menu -- which could also include
    "Just do it, I know what --uninstall does")

--
Regards,
Bengt Richter





  reply	other threads:[~2024-04-11 12:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  8:52 bug#70215: Documentation about uninstalling Shalok Shalom via Bug reports for GNU Guix
2024-04-11  0:08 ` Rostislav Svoboda
2024-04-11 12:36   ` bokr [this message]
2024-04-11 13:10     ` Rostislav Svoboda
2024-04-13  6:25       ` Bengt Richter
2024-05-07 18:55         ` Simon Tournier

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=20240411123621.GA2976@LionPure \
    --to=bokr@bokr.com \
    --cc=70215@debbugs.gnu.org \
    --cc=rostislav.svoboda@gmail.com \
    /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).