From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: more package transformations: overrides
Date: Fri, 24 Mar 2023 08:32:32 -0400 [thread overview]
Message-ID: <871qle1g9r.fsf@gmail.com> (raw)
In-Reply-To: <87cz4zijag.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 23 Mar 2023 10:32:38 +0100")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>>> Considering that the transformations API assumes that you understand
>>> that higher order functions exist and what to do with them, I think it
>>> would be good to offer a slightly less advanced method of overriding
>>> packages.
>>>
>>> Manifests can do anything, but this also makes them rather intimidating
>>> for many of my colleagues.
>>
>> OK; then my question would be: why stop at transformations? Perhaps we
>> could simply have a way to feed arbitrary guix command line arguments
>> from a file, e.g.
>>
>> guix shell --args-file=my-arguments.txt
>
> The transformations command line options are rather verbose:
>
> --with-input=python-pytorch=python-pytorch-with-extra-features
>
> I think it would improve usability to be able to use the *same* names in
> an override file. Got a package with name “python-pytorch” in that
> file? It replaces “python-pytorch” in the graph.
It's still a bit too abstract in my mind. Could you please provide a
skeletton of what the overrides file would look like?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-24 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 9:55 more package transformations: overrides Ricardo Wurmus
2023-03-22 11:00 ` Josselin Poiret
2023-03-22 14:38 ` Ludovic Courtès
2023-03-22 18:09 ` Maxim Cournoyer
2023-03-22 20:36 ` Ricardo Wurmus
2023-03-23 2:56 ` Maxim Cournoyer
2023-03-23 9:32 ` Ricardo Wurmus
2023-03-24 8:21 ` Sarthak Shah
2023-03-24 12:30 ` Maxim Cournoyer
2023-03-24 14:05 ` Sarthak Shah
2023-03-24 16:09 ` Maxim Cournoyer
2023-03-24 12:32 ` Maxim Cournoyer [this message]
[not found] ` <87r0tdgqbu.fsf@elephly.net>
2023-03-26 2:26 ` Maxim Cournoyer
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=871qle1g9r.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).