unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Peter Polidoro <peter@polidoro.io>
Cc: zimoun <zimon.toutoune@gmail.com>,  guix-science@gnu.org
Subject: Re: Reproducible Project Environments
Date: Thu, 09 Dec 2021 21:33:37 +0100	[thread overview]
Message-ID: <8735n1frha.fsf@gnu.org> (raw)
In-Reply-To: <867dcfw3km.fsf@polidoro.io> (Peter Polidoro's message of "Wed, 08 Dec 2021 09:30:34 -0500")

Hi Peter,

Peter Polidoro <peter@polidoro.io> skribis:

>>
>> From my point of view, if we are speaking of a project gluing many
>> thing
>> to produce analysis, then a Git repo with:
>>
>>   - manifest.scm containing package set for the project
>>   - channels.scm containing the revision
>>   - all your files
>
> Does 'guix describe - f channels' always return a list of all of the
> user's channels? If I include a channels.scm file in a project, it
> would be nice if it only contained the channels necessary to build and
> run the packages within that project.

Yes, it includes all the channels your ‘guix’ command is using, but you
could easily edit it to remove unnecessary channels.

> Is it possible to use the guix.scm or manifest.scm file when
> generating the channels.scm file so it only includes the necessary 
> channels? Would I need to create a temporary project profile first and
> then use that to filter the channel list?

I think the workflow in general would be:

  1. Write ‘manifest.scm’ (or ‘guix.scm’).

  2. Run ‘guix describe -f channels > channels.scm’.

  3. If you know that ‘channels.scm’ contains more than what’s strictly
     needed, remove it.

In theory it should be possible to automatically determine from the
manifest which channels are definitely required, but there currently
isn’t a command to do the filtering in step #3 for yourself.

HTH!

Ludo’.


      reply	other threads:[~2021-12-09 20:33 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
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 [this message]

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=8735n1frha.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-science@gnu.org \
    --cc=peter@polidoro.io \
    --cc=zimon.toutoune@gmail.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.
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).