On Fri, Oct 21, 2016 at 03:44:47PM -0400, Leo Famulari wrote:
> On Fri, Oct 21, 2016 at 02:53:02PM +0300, Efraim Flashner wrote:
> > On Fri, Oct 21, 2016 at 12:56:08PM +0200, Hartmut Goebel wrote:
> > > Hi,
> > > 
> > > testing the new python build system I’m seeking for some way to build
> > > *many* packages in order.
> > > 
> > > Of course I can just run `guix build` with the list of packages to be
> > > build. But when building all python packages, the list gets rather long
> > > and does not fit into one call of `guix build` (due to the number of
> > > arguments xargs passes to the command is restricted). Thus only
> > > partitions of the packages are build in order.
> > >  
> > > So I need some way for passing *all* packages to be build to `guix build`.
> > > 
> > > Any hints?
> > > 
> > 
> > If you want to build all packages that are python- or python2-, then you
> > can call 'guix build $(guix package -A ^python | cut -f1)'
> > 
> > If you want all the packages that rely on python or python-2, then you
> > can call 'guix build $(guix refresh -l python python@2 | cut -d':' -f2)'
> > 
> > Both of these as written will stop when they encounter a package that
> > doesn't build. I'm sure there's also a scheme-y way of doing it.
> 
> I've been doing this to build all users of pytest, and I passed
> --keep-going to `guix build`. I think that should work here, right?

I suppose it depends on if you want to fix each build error as it
happens. There's not a way that I can think of to say "only build the
ones that build successfully on hydra" or "print me a list of successes
and failures at the end"


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted