Documentation about uninstalling

  • Open
  • quality assurance status badge
Details
4 participants
  • bokr
  • Rostislav Svoboda
  • Shalok Shalom
  • Simon Tournier
Owner
unassigned
Submitted by
Shalok Shalom
Severity
normal
S
S
Shalok Shalom wrote on 5 Apr 10:52 +0200
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
o2kUMVhyarvXUYxaKZ_CmY-_A6enzIq54AvchErbuYIO9G8vLx58t572Dr9RyBAU1gAFmFH-7FwTb6E79PkZIWNddtzCque-UwP-xn9mfEY=@protonmail.ch
I have installed Guix with the script, and now cannot find the part of the documentation, that explains how to uninstall it.

Sicher versendet mit [Proton Mail](https://proton.me/).
Attachment: file
R
B
B
bokr wrote on 11 Apr 14:36 +0200
Re: bug#70215: Documentation about uninstalling
(name . Rostislav Svoboda)(address . rostislav.svoboda@gmail.com)(address . 70215@debbugs.gnu.org)
20240411123621.GA2976@LionPure
On +2024-04-11 02:08:35 +0200, Rostislav Svoboda wrote:
Toggle quote (6 lines)
> 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
R
R
Rostislav Svoboda wrote on 11 Apr 15:10 +0200
(address . bokr@bokr.com)(address . 70215@debbugs.gnu.org)
CAEtmmewouqjdqtJzzaea6CNZrnYu=DneqLjqePzwMASPumL-1A@mail.gmail.com
Toggle quote (4 lines)
> ./guix-install.sh --uninstall
> [...]
> That sounds dangerous

Yeah a bit.

Toggle quote (6 lines)
> -- 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")

Eeeh? I don't understand what you mean.

Nevertheless, `./guix-install.sh --dry-run --uninstall` would be nice.
However the script is over 800 lines long. In bash! :-(
IMO before increasing script complexity with a new feature, we should
rewrite it to some reasonable language, preferably Guile Scheme. Or at
least Python.

Cheers Bost
B
B
Bengt Richter wrote on 13 Apr 08:25 +0200
(name . Rostislav Svoboda)(address . rostislav.svoboda@gmail.com)(address . 70215@debbugs.gnu.org)
20240413062559.GA15939@LionPure
On +2024-04-11 15:10:56 +0200, Rostislav Svoboda wrote:
Toggle quote (15 lines)
> > ./guix-install.sh --uninstall
> > [...]
> > That sounds dangerous
>
> Yeah a bit.
>
> > -- 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")
>
> Eeeh? I don't understand what you mean.
>

Sorry, I should have explained.

I just wanted a simple way to save /exactly/ what uninstall would delete.
so it wouldn't be "irrevocable," in case the uninstall is too eager about its job ;)

A dry run of that size would be a scrolling blur, I think, and not much use unless
captured, and then it would take a lot of boring unreliable reading before you could
decide for sure that it was ok to do the uninstall.

Maybe guix pack could make a tarball of exactly what uninstall would delete, e.g.,
guix pack --uninstall-victim-files

with options of where to write it.
Toggle quote (7 lines)
> Nevertheless, `./guix-install.sh --dry-run --uninstall` would be nice.
> However the script is over 800 lines long. In bash! :-(
> IMO before increasing script complexity with a new feature, we should
> rewrite it to some reasonable language, preferably Guile Scheme. Or at
> least Python.
>

Well, guix pack is already scheme, right? Why couldn't it invoke uninstall after
safely having completed packing the uninstall-victim-files ?

WDYT? Simon? Ludo? Anyone? :)

Toggle quote (2 lines)
> Cheers Bost

--
Regards,
Bengt Richter
S
S
Simon Tournier wrote on 7 May 20:55 +0200
(address . 70215@debbugs.gnu.org)
87frut1mfw.fsf@gmail.com
Hi,

I mark this bug as done since the documentation already contains how to
uninstall.

On sam., 13 avril 2024 at 08:25, Bengt Richter <bokr@bokr.com> wrote:

Toggle quote (2 lines)
>> Nevertheless, `./guix-install.sh --dry-run --uninstall` would be nice.

Well, it would be easy to write a Bash function wrapping ’rm’ and
displaying the files instead of removing them.

Who wants to give a try? ;-)

Toggle quote (5 lines)
>> However the script is over 800 lines long. In bash! :-(
>> IMO before increasing script complexity with a new feature, we should
>> rewrite it to some reasonable language, preferably Guile Scheme. Or at
>> least Python.

The maintenance burden Bash vs Python is an opinion. :-)

Well, a rewrite in Scheme/Guile would require to have Guile already
installed to run such script. And that’s not an assumption I would
do. ;-)


Toggle quote (3 lines)
> Well, guix pack is already scheme, right? Why couldn't it invoke uninstall after
> safely having completed packing the uninstall-victim-files ?

Well, it’s appears to me an heavy hammer. The best seems to have an
option displaying the files that need to be removed for uninstalling.

Let’s discuss that on guix-devel. Because it’s not related to a
bug. :-)


Cheers,
simon
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 70215@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70215
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch