Re: Google Summer of Code 2023 Inquiry

Hi, Spencer Skylar Chan writes: > One approach could be to add CWL import/export capabilities to > GWL. Then Snakemake/GWL conversion would be a 2 step process, using > CWL as an intermediate step: > > 1. Snakemake -> CWL > 2. CWL -> GWL This seems doable. > However, CWL is not as expressive a

Re: Google Summer of Code 2023 Inquiry

Dear Spencer, I am a bit worried about your proposed project is too focused on replacing python with guile. I think the project would benefit more from making python users more comfortable productively using Guix tools in concert with the tools they are already comfortable with. I'm wondering

Re: more package transformations: overrides

Hello, Sarthak Shah writes: > Hello, > >> By separate file or stdin your really mean stdin, correct? As in: >> >> --8<---cut here---start->8--- >> guix something < args.txt or >> echo "$args" | guix something >> --8<---cut here---end--

Re: more package transformations: overrides

Hi Ricardo, Ricardo Wurmus writes: > Maxim Cournoyer 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 >>> package

Re: more package transformations: overrides

Hello, > By separate file or stdin your really mean stdin, correct? As in: > > --8<---cut here---start->8--- > guix something < args.txt or > echo "$args" | guix something > --8<---cut here---end--->8--- > > One note: since t

Re: more package transformations: overrides

Hello! Thanks for the CC, Josselin! I like Maxim's idea of providing all kinds of arguments through a separate file or stdin. Here's a tiny proof-of-concept script implementing that: -guix-shell-with-args.sh #!/usr/bin/env bash argstr="" while read line do argstr="$argstr $line" done < "$

Re: more package transformations: overrides

Hi! Sarthak Shah writes: > Hello! > Thanks for the CC, Josselin! > I like Maxim's idea of providing all kinds of arguments through a separate > file or stdin. > Here's a tiny proof-of-concept script implementing that: > -guix-shell-with-args.sh > #!/usr/bin/env bash > argstr="" > while r

[RFC] Cosmetic changes to define-configuration usage

Forwarded from: & [1] --8<---cut here---start->8--- apteryx: IMO the spacing between the fields should have been kept it makes things easier to read it's a nightmare if the records grow very large mirai: I w

Re: Hello Guix!

Hi Vijaya, A very warm welcome to Guix! As mentioned by (, contributions towards decentralization of substitutes are very welcome! Guix, Vijaya has been in contact with me and some concrete ideas for a GSoC proposal are in the making (I'll let Vijaya ellaborate on the ideas). I believe Vijaya

Re: Guix QA: build status "unknown"

Andy Tai writes: > I don't know if it is just me, but Guix QA recently seems to always > show build status unknown when what really happens was the build > succeeds on both x86-64 and aarch64 but on other platforms it was in > "scheduled" state but the scheduled build never actually got run. I

how to print values inside shepherd service gexp

Hello. I probably have all phases screwed up in my head now. (shepherd-service (start #~(make-forkexec-constructor some-command #:directory (pk #$twgter-directory) #:log-file (pk #$twgter-log-file)) )) If we instantiate this process in ou