From: Ricardo Wurmus <rekado@elephly.net>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Olivier Dion via <help-guix@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Subject: Re: Questions regarding substitutes with debug output
Date: Fri, 29 Apr 2022 22:08:27 +0200 [thread overview]
Message-ID: <871qxf1wh7.fsf@elephly.net> (raw)
In-Reply-To: <877d77rhhx.fsf@laura>
Olivier Dion <olivier.dion@polymtl.ca> writes:
> On Fri, 29 Apr 2022, Ricardo Wurmus <rekado@elephly.net> wrote:
>>> Even if I were to import locally defined packages, their dependencies
>>> would come from the Guix's main channel!
>>
>> What would you think about WITH-CHANNELS that would accept a list of
>> channels and evaluate any package reference in its body within an
>> inferior of those channels?
>>
>> E.g.
>>
>> (with-channels %my-channels
>> (package
>> (name "yay")
>> …
>> (inputs
>> (list foo bar baz)) ;these are all looked up in %my-channels
>> …
>> (license gpl3+)))
>
> What about dependencies? Says I have the following graph:
>
> G <- Guix's channel
> C <- My channel
>
> P@V <- My package at version V from C
> D@U <- Dependency of P at version U from G
>
> The `guix time-machine` allows me to pin the commits of G and C and thus
> pinning V and U. Would that work the with WITH-CHANNELS ?
Exactly the same way. The first argument to WITH-CHANNELS would be
(cons C G) and thus P and D would be picked from the set of C and G. C
and G can be specified with exact commits or branches, just like the
--channels option to “guix time-machine”.
We already have all the tools for WITH-CHANNELS — that’s (guix
inferior). We just don’t have a convenient syntax to do this without a
lot of boilerplate.
--
Ricardo
next prev parent reply other threads:[~2022-04-29 20:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 17:32 Questions regarding substitutes with debug output Olivier Dion via
2022-04-22 4:22 ` Maxim Cournoyer
2022-04-22 14:29 ` Olivier Dion via
2022-04-24 3:38 ` Maxim Cournoyer
2022-04-24 14:56 ` Olivier Dion via
2022-04-25 4:10 ` Maxim Cournoyer
2022-04-28 8:13 ` zimoun
2022-04-28 8:58 ` Ricardo Wurmus
2022-04-28 14:11 ` Olivier Dion via
2022-04-28 14:18 ` Ricardo Wurmus
2022-04-28 14:25 ` Olivier Dion via
2022-04-29 5:06 ` Ricardo Wurmus
2022-04-28 14:20 ` Olivier Dion via
2022-04-29 8:49 ` zimoun
2022-04-29 14:47 ` Olivier Dion via
2022-04-29 16:01 ` Ricardo Wurmus
2022-04-29 16:17 ` Olivier Dion via
2022-04-29 20:08 ` Ricardo Wurmus [this message]
2022-04-29 20:53 ` Olivier Dion via
2022-05-09 10:33 ` zimoun
2022-05-09 13:33 ` Ricardo Wurmus
2022-05-09 14:37 ` zimoun
2022-04-29 16:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qxf1wh7.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=olivier.dion@polymtl.ca \
--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.
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.