unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: jgart <jgart@dismail.de>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: uninstall/unmanage guix home on my foreign system
Date: Tue, 09 Aug 2022 22:25:47 +0200	[thread overview]
Message-ID: <87iln14110.fsf@gnu.org> (raw)
In-Reply-To: <20220725174352.GC3612@gac> (jgart@dismail.de's message of "Mon,  25 Jul 2022 17:43:52 -0500")

Hi jgart,

jgart <jgart@dismail.de> skribis:

> How can I "uninstall" guix home or have it not manage my dotfiles or a particular subset of dotfiles that I no longer want managed?

Good question; I don’t think there’s an easy way to escape, it’s a bit
of a trap.  :-)

What I would do is something like this (untested):

  1. Make sure packages you need are installed on the system or in
     ~/.guix-profile, by running, say:

       guix package --export-manifest -p ~/.guix-home/profile/manifest > \
         ~/my-manifest.scm

       guix package -m ~/my-manifest.scm

   2. Restore dot files that were managed by Guix Home, for example by
      copying your original dot files from a backup such as the one
      created by ‘guix home reconfigure’:

        for i in .bashrc .bash_profile # add others here
        do
          rm "$HOME/$i"
          cp -v "$HOME/guix-home-backup-whatever-its-called/$i" "$HOME"
        fi

   3. Remove your home profile:

       rm -v ~/.guix-home /var/guix/profiles/per-user/$USER/guix-home*

IWBN to have a ‘guix home’ subcommand to do that automatically.

HTH!

Ludo’.


      reply	other threads:[~2022-08-09 20:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 22:43 uninstall/unmanage guix home on my foreign system jgart
2022-08-09 20:25 ` Ludovic Courtès [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=87iln14110.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    /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).