From: zimoun <zimon.toutoune@gmail.com>
To: Tanguy LE CARROUR <tanguy@bioneland.org>,
Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Notes from discussion on Quality Assurance from the 10 Years of Guix event
Date: Mon, 24 Oct 2022 09:34:09 +0200 [thread overview]
Message-ID: <87wn8pisjy.fsf@gmail.com> (raw)
In-Reply-To: <166653965392.19847.3217461018929572554@localhost>
Hi Tanguy,
On dim., 23 oct. 2022 at 17:40, Tanguy LE CARROUR <tanguy@bioneland.org> wrote:
>> guix package --export-manifest > /tmp/my-pkgs.scm
>> guix refresh -m /tmp/my-pkgs.scm 2>&1 | ...
>
> I'm not using manifest (anymore). I used to, but for the time being, I'm using
> `divenv` + `guix shell` and I'm quite happy with that setup.
Note that the first command above creates the manifest for you.
Usually, it works well enough. :-)
Well, ’direnv’ + ’guix shell’ but you have a manifest, no? I mean how
does ’guix shell’ know what to provide inside this new shell?
For what it is worth, I have used similar workflow but I have been bored
to run “guix pull”, do some stuff unrelated to ’project’, then later be
back on ’project’ and then have failures. Instead, my workflow is
splited into 2 ways depending on my phase of the Moon. Either, I create
a profile inside the project directory. Either, I use channels.scm +
manifest.scm and often run via ’guixify’ script (see below); e.g.,
guixify foo # run foo using the Guix environment
guixify # enter in the environment
Maybe, ’direnv’ would do a better job. The good point is that
channels.scm and manifest.scm are included in the Git tree of the
project. And they can be re-used with ’guix pack -f docker -m
manifest.scm’ to generate Docker pack that I can share with colleagues.
--8<---------------cut here---------------start------------->8---
#!/bin/sh
guix time-machine -C channels.scm \
-- shell --pure \
-m manifest.scm \
-- $@
--8<---------------cut here---------------end--------------->8---
Cheers,
simon
next prev parent reply other threads:[~2022-10-24 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 15:55 Notes from discussion on Quality Assurance from the 10 Years of Guix event Christopher Baines
2022-10-05 14:01 ` Tanguy LE CARROUR
2022-10-05 16:51 ` Christopher Baines
2022-10-09 15:58 ` Tanguy LE CARROUR
2022-10-18 16:19 ` Tanguy LE CARROUR
2022-10-19 9:57 ` zimoun
2022-10-23 15:40 ` Tanguy LE CARROUR
2022-10-24 7:34 ` zimoun [this message]
2022-10-24 11:43 ` Tanguy LE CARROUR
2022-10-23 21:33 ` kiasoc5
2022-10-19 19:31 ` Efraim Flashner
2022-10-23 15:48 ` Tanguy LE CARROUR
2022-10-24 7:44 ` zimoun
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=87wn8pisjy.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).