From: Julien Lepiller <julien@lepiller.eu>
To: guix-science@gnu.org, Peter Polidoro <peter@polidoro.io>
Subject: Re: Reproducible Project Environments
Date: Mon, 06 Dec 2021 11:16:56 -0500 [thread overview]
Message-ID: <3217E051-A339-46F8-911C-178927DA3435@lepiller.eu> (raw)
In-Reply-To: <86lf0x3f9c.fsf@polidoro.io>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
When my projects are missing a dependency from guix, or use a specific version, I simply specify them in my guix.scm for tge project, so it's just as easy to create the environment. I remove it as soon as I contribute it to guix. I would only use a separate channel if multiple projects require the same dependency and it.s taking a lot of time to get it into guix.
[-- Attachment #2: Type: text/html, Size: 406 bytes --]
next prev parent reply other threads:[~2021-12-06 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 14:18 Reproducible Project Environments Peter Polidoro
2021-12-06 16:16 ` Julien Lepiller [this message]
2021-12-06 18:09 ` Peter Polidoro
2021-12-06 19:52 ` Efraim Flashner
2021-12-06 16:58 ` zimoun
2021-12-06 18:13 ` Peter Polidoro
2021-12-08 14:30 ` Peter Polidoro
2021-12-09 20:33 ` Ludovic Courtès
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=3217E051-A339-46F8-911C-178927DA3435@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-science@gnu.org \
--cc=peter@polidoro.io \
/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).