unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Andreas Reuleaux <rx@a-rx.info>, help-guix <help-guix@gnu.org>
Subject: Re: guix on a debian system (with packages from experimental) - recommended day to day routine?
Date: Thu, 02 Sep 2021 21:58:40 +0200	[thread overview]
Message-ID: <86zgsu21hr.fsf@gmail.com> (raw)
In-Reply-To: <87mtoz695b.fsf@softland>

Hi

On Mon, 30 Aug 2021 at 01:58, Andreas Reuleaux <rx@a-rx.info> wrote:

> Now, long story short: I wonder -- two things:
>
> (1) what good is the debian /usr/bin/guix at all for me? - and

I am not sure to understand the question.

In short, /usr/bin/guix is not useful for the user because the user uses
~/.config/guix/current/bin/guix instead.  However, the user uses the
daemon which is /usr/bin/guix-daemon.  Except if you changed the SystemD
configuration.

When you run “guix pull” as a user, ~/.config/guix/current/bin/guix is
updated but not the daemon which is running with root privileges.

To update this daemon, you can run “guix pull” as root.  Note the daemon
changes really barely.  You can also update the daemon with “apt upgrade
guix” but I am not sure Guix is often updated.


> (2) what daily routine is recommended for upgrading/reconfiguring my
> whole guix system, with /usr/bin/guix perhaps - if any routine at all?
>
> Obviously, the
> --8<---------------cut here---------------start------------->8---
> sudo guix system reconfigure /etc/config.scm
> --8<---------------cut here---------------end--------------->8---
> step does not apply, as there is no /etc/config.scm now on my system
> (it is running debian after all).

I do not think it makes because it is Guix on foreign distro and not
Guix System.

> Should I try to do something similar nevertheless once in a while?
> (and as what user: my unprivileged rx, or as root)?

Well, running Guix on Debian (installed via the script), I do:

  $ guix pull

once a week or more often, then

  $ guix package -u

when I am in good mood. :-)  Every good Moon phase, I do as root:

  # guix pull
  # systemctl restart guix-daemon.service 

Aside, I recommend you to read:

<https://guix.gnu.org/cookbook/en/guix-cookbook.html#Advanced-package-management>

Other said, my default profile ~/.guix-profile contains almost nothing.
And I have several profiles living at ~/.config/guix/profiles/ which I
update time to time.  Then I also have profiles living in the folder of
my project’s directories.

Also, I declare the packages a profile requires using a file
manifest.scm then I store “guix describe -f channels” as channels.scm
when I create the profiles. It allows to recreate elsewhere with:

  guix time-machine -C channels -- package -m manifest.scm

> Clear some cache maybe, etc.?

Time to time, I run “guix gc” with various options.


Hope that helps,
simon





  reply	other threads:[~2021-09-02 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30  0:58 guix on a debian system (with packages from experimental) - recommended day to day routine? Andreas Reuleaux
2021-09-02 19:58 ` zimoun [this message]
2021-09-02 21:35   ` Andreas Reuleaux

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=86zgsu21hr.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rx@a-rx.info \
    /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).