unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tangonov <tn@eml.cc>
To: help-guix@gnu.org
Subject: Guix home package confusion
Date: Tue, 14 Jun 2022 08:05:45 -0700	[thread overview]
Message-ID: <878rpz9t3f.fsf@eml.cc> (raw)

I am trying out guix for the first time and feel like I may have 
jumped in head-first into the shallow end of the pool.

I had started out with using guix package for my packages and 
updated my env for around 30 generations. Then I discovered guix 
home and thought "hey, that may be better".

I set up guix home following the documentation and it created my 
first home generation and completely re-installed my packages.

However, after subsequent changes to my home config, a guix home 
reconfigure is now attempting to re-install (and build) my 
packages all over again, despite never having run a guix pull.

I tried to "undo" the initialization of guix home as I feel like I 
maybe should stick to the "older way" for a while longer while I 
get the hang of Guile Scheme and try not to change too much at 
once. I have been unable to revert my initial revision, or find a 
clear path back without doing something dramatic.

With all of my history in mind, I have 3 questions:

1. Is there a supported way to apply incremental changes in guix 
home, without re-doing (and re-compiling) all of my software?
2. Is there a supported way to revert back to just using GNU Stow 
and guix package?
3. If I can be happy with guix home, is there any supported way to 
remove potential bloat from having run guix package for 30 
generations?

Thanks for the incredible software and help, if you're able.

-- 

- Tangonov


             reply	other threads:[~2022-06-14 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 15:05 Tangonov [this message]
2022-06-14 18:41 ` Guix home package confusion Efraim Flashner
2022-06-15  3:20   ` Tangonov
2022-06-15  5:38     ` Tangonov
2022-06-15  6:47       ` Sébastien Rey-Coyrehourcq
2022-06-15 13:48         ` Gary Johnson

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=878rpz9t3f.fsf@eml.cc \
    --to=tn@eml.cc \
    --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).