all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, 白い熊 <help-guix_gnu.org@sumou.com>
Subject: Re: Guix development on GuixSD, recommended setup and process
Date: Tue, 31 Mar 2020 08:32:14 -0400	[thread overview]
Message-ID: <D1B9E659-E168-43D3-A1D0-A5995C11B43A@lepiller.eu> (raw)
In-Reply-To: <7c52f508-7b83-4e56-9123-634cb23b00b7@localhost>

Le 31 mars 2020 07:38:44 GMT-04:00, "白い熊" <help-guix_gnu.org@sumou.com> a écrit :
>Hi Guix:
>
>I'd like to install GuixSD and experiment with Guix git development and
>contributing. For this I'd like to ask what the proper recommended
>setup would be.
>
>Concretely, how should I go about it:
>
>— First, logically, install GuixSD and set the system up.
>— Then clone the Guix git.
>
>Then though — would it be “smarter” to git update always the checkout
>and run programs from within the preenv leaving the underlying GuixSD
>system minimal for what needs to be set up in the system?
>
>I.e. all user applications, like browser, office, would be installed
>and run from the git version?
>
>Or would be more recommended to install and run these from within the
>base GuixSD system?
>
>Why either?
>
>Is there any other interface between the GuixSD system and the git
>version I should be aware of or utilize?
>
>Many thanks for your advice, if any.

Hi 白い熊,

I personnaly use the git checkout only to apply patches and try changes. It is sometimes in a state that's broken because of my modifications, so I prefer not to use it. I also have channels, and sometimes they break because of changes in guix. In times like this, it is more convenient to roll back, wait for a fix in the channels and pull again.

In terms of packages, they are the same: there is no difference between the hash of a package built from a git commit and a package built from guix (pulled at the same commit), so there is no more duplication than usual, especially since I pull every few days anyway.

My system is always minimal, and I install packages in my user profile (or actually my home manager's profile).

HTH!

  reply	other threads:[~2020-03-31 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 11:38 Guix development on GuixSD, recommended setup and process 白い熊
2020-03-31 12:32 ` Julien Lepiller [this message]
2020-03-31 13:59   ` 白い熊
2020-03-31 15:48     ` Julien Lepiller

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D1B9E659-E168-43D3-A1D0-A5995C11B43A@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=help-guix_gnu.org@sumou.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.