Re: Using gexp for the #:builder arg of build systems

2017-09-29 Thread Maxim Cournoyer
Hi Ludovic! l...@gnu.org (Ludovic Courtès) writes: > Hello! > > Maxim Cournoyer skribis: > >> After reading Ludovic's paper about gexps, I was curious to try it in a >> package definition. Is this supported yet? > > It’s not possible in current master. There’s work for that in > ‘wip-gexp’, tha

Re: Using gexp for the #:builder arg of build systems

2017-09-29 Thread Ludovic Courtès
Hello! Maxim Cournoyer skribis: > After reading Ludovic's paper about gexps, I was curious to try it in a > package definition. Is this supported yet? It’s not possible in current master. There’s work for that in ‘wip-gexp’, that I’d like to merge in ‘core-updates’ Real Soon (I’ve rebased it l

Re: gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5

2017-09-29 Thread Maxim Cournoyer
> Efraim Flashner writes: > >> On Fri, Sep 29, 2017 at 07:21:27PM +0800, Huang, Ying wrote: >>> Hi, All, >>> >>> I use the guix git. After not upgrade the code for quite some time >>> (several months?), today after `git pull`, `guix environment guix` >>> report the following error. How to deal

Re: gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5

2017-09-29 Thread Huang, Ying
Efraim Flashner writes: > On Fri, Sep 29, 2017 at 07:21:27PM +0800, Huang, Ying wrote: >> Hi, All, >> >> I use the guix git. After not upgrade the code for quite some time >> (several months?), today after `git pull`, `guix environment guix` >> report the following error. How to deal with it?

Re: gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5

2017-09-29 Thread Huang, Ying
Andy Wingo writes: > On Fri 29 Sep 2017 13:21, "Huang, Ying" writes: > >> I use the guix git. After not upgrade the code for quite some time >> (several months?), today after `git pull`, `guix environment guix` >> report the following error. How to deal with it? > > Remove .go files from your

Re: gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5

2017-09-29 Thread Efraim Flashner
On Fri, Sep 29, 2017 at 07:21:27PM +0800, Huang, Ying wrote: > Hi, All, > > I use the guix git. After not upgrade the code for quite some time > (several months?), today after `git pull`, `guix environment guix` > report the following error. How to deal with it? > > Backtrace: > In ice-9/boot-9

Re: ‘guix pack’ & entry point

2017-09-29 Thread Ludovic Courtès
Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> Bonus: what would the tarball backend do with the entry point? Ignore it? > > It should end up as a script in the tarball IMO. With an easily recognizable fixed name? Like /init or /run? > Maybe we want a more general feature here. For

Re: gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5

2017-09-29 Thread Andy Wingo
On Fri 29 Sep 2017 13:21, "Huang, Ying" writes: > I use the guix git. After not upgrade the code for quite some time > (several months?), today after `git pull`, `guix environment guix` > report the following error. How to deal with it? Remove .go files from your git checkout. A change in Sch

gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5

2017-09-29 Thread Huang, Ying
Hi, All, I use the guix git. After not upgrade the code for quite some time (several months?), today after `git pull`, `guix environment guix` report the following error. How to deal with it? Backtrace: In ice-9/boot-9.scm: 230:29 19 (map1 _) 230:29 18 (map1 _) 230:29 17 (map1 _) 23

Re: ‘guix pack’ & entry point

2017-09-29 Thread Ricardo Wurmus
Ludovic Courtès writes: > Bonus: what would the tarball backend do with the entry point? Ignore it? It should end up as a script in the tarball IMO. Maybe we want a more general feature here. For example, we had the problem that /etc/environment is not actually sourced by default. Maybe wha

Re: ‘guix pack’ & entry point

2017-09-29 Thread Vincent Legoll
Hello, I think you're speaking of the "CMD" entry from the Dockerfile. You can specify a shell commandline, not just a single executable. This is nice and very useful because you sometimes don't want to embed a shell script to launch a simple pipeline. -- Vincent Legoll