Re: using Cuirass to track a guix packages' git

Jan Nieuwenhuizen writes: > Mathieu Lirzin writes: > >> David Craven writes: >> >>> I think the web interface and the json API are two different >>> "projects". >> >> Agreed. > > Oh! Then why choose json (poor-man's-sexps?) over sexps? I'm mostly > just using

Re: using Cuirass to track a guix packages' git

Mathieu Lirzin writes: > David Craven writes: > >> I think the web interface and the json API are two different >> "projects". > > Agreed. Oh! Then why choose json (poor-man's-sexps?) over sexps? I'm mostly just using sexps with read and write, and pipe through json

Re: using Cuirass to track a guix packages' git

David Craven writes: > I think the web interface and the json API are two different > "projects". Agreed. >> just a matter of knowing how to do the javascript stuff. :) > > Many people think that JS is a toy language, JS the good parts is a > weekend read (like 100p or

Re: using Cuirass to track a guix packages' git

I think the web interface and the json API are two different "projects". > just a matter of knowing how to do the javascript stuff. :) Many people think that JS is a toy language, JS the good parts is a weekend read (like 100p or something) that might change your perspective and covers

Re: using Cuirass to track a guix packages' git

Jan Nieuwenhuizen writes: > Mathieu Lirzin writes: > >>> Yes, I think I found this, I can see json in my browser window...but >>> that's not really a web view yet (no criticism, I'm just wondering...) >> >> Sorry I misread what you meant by web view. I don't have much >>

Re: using Cuirass to track a guix packages' git

Mathieu Lirzin writes: >> Yes, I think I found this, I can see json in my browser window...but >> that's not really a web view yet (no criticism, I'm just wondering...) > > Sorry I misread what you meant by web view. I don't have much > experience in Web programming, I guess an "easy" way (for a

Re: using Cuirass to track a guix packages' git

Jan Nieuwenhuizen writes: > Mathieu Lirzin writes: > >>> Thanks! I'd really love to get a working Guix-based ci system and >>> Cuirass is already very close to the minimal set that I need. I have >>> a working patch to add building of VMs (a la hydra/guix-system.scm) but >>>

Re: using Cuirass to track a guix packages' git

Mathieu Lirzin writes: > Intuitively I would prefer "#:compile?" but both are OK, so we can stick > with "#:no-compile?" if that's more convenient. Yes, me too. Let's see where this goes, it can prolly be changed easily later. >>> Can you send the updated patches? >> >> Sure, find attached. >

Re: using Cuirass to track a guix packages' git

Jan Nieuwenhuizen writes: > Mathieu Lirzin writes: > > Hi Mathieu! > >>> I had some trouble with the #:no-compile? option, it's currently >>> specified twice. On the Cuirass side I think it should be a property >>> of the spec, but it seems it gets only passed as part of the

Re: using Cuirass to track a guix packages' git

Jan Nieuwenhuizen writes: Oops, sent too soon, patch 2 needed this fix diff --git a/src/cuirass/database.scm b/src/cuirass/database.scm index 0dcf544..5d3922b 100644 --- a/src/cuirass/database.scm +++ b/src/cuirass/database.scm @@ -141,7 +141,7 @@ INSERT INTO Specifications\

Re: using Cuirass to track a guix packages' git

Mathieu Lirzin writes: Hi Mathieu! >> I had some trouble with the #:no-compile? option, it's currently >> specified twice. On the Cuirass side I think it should be a property >> of the spec, but it seems it gets only passed as part of the >> arguments. Ideas? > > OK, I think I got it. With

Re: using Cuirass to track a guix packages' git

Hello Jan, Jan Nieuwenhuizen writes: > I had some trouble with the #:no-compile? option, it's currently > specified twice. On the Cuirass side I think it should be a property > of the spec, but it seems it gets only passed as part of the > arguments. Ideas? OK, I think I got

Re: using Cuirass to track a guix packages' git

Hello Jan, Jan Nieuwenhuizen writes: > I have been playing with Cuirass and I like it a lot! Cool. :) I want to let you know that I have just started looking at your patches. I have been quite busy lately. Sorry for the latency. Next time I will let you know sooner if you