Re: proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 10:49 PM, Ludovic Courtès wrote: > Florian Paul Schmidt skribis: > >> Oh, I wasn't even aware there was a DB. I had a more functional >> picture in mind where there was a map > > See >

Re: proposal: make build failures explicit results in the store

Florian Paul Schmidt skribis: > Oh, I wasn't even aware there was a DB. I had a more functional > picture in mind where there was a map See . > package definition -> entr(y|ies) in store The store is at a

Re: proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 03:19 PM, Florian Paul Schmidt wrote: > Oh, I wasn't even aware there was a DB. I had a more functional > picture in mind where there was a map > I guess I should have written "simpler" instead of "more functional".. Flo - --

Re: proposal: make build failures explicit results in the store

Florian Paul Schmidt writes: > Hi, > > currently I'm trying my hands on building _all_ available packages on > the x86_64 platform in a qemu-vm (with the intended aim to later > publish them to maybe take some load off hydra), but I came across an > issue that might have an

proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, currently I'm trying my hands on building _all_ available packages on the x86_64 platform in a qemu-vm (with the intended aim to later publish them to maybe take some load off hydra), but I came across an issue that might have an easy solution

Re: proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 02:22 PM, Ludovic Courtès wrote: > taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > >> You can run the Guix daemon with the switch --cache-failures and >> it will do pretty much exactly what you want. :-) > > Yep.