BTW, I’ve been traveling lately, and I’ve really missed ‘guix prefetch’.
So if you have spare time to pour into it, or if someone else wants to
take it over, that’d be nice!
Ludo’.
BTW, I’ve been traveling lately, and I’ve really missed ‘guix
prefetch’.
Heh, that was the motivation.
So if you have spare time to pour into it, or if someone else wants to
take it over, that’d be nice!
I doubt so, unfortunately. So please do take it over if you can.
pgpMOhIZmPKkm.pgp
Does the installation seem sane, basically? Do ‘guix build’, ‘guix
package’ etc. work somehow, or not even?
Turns out I can’t even build ‘hello’
Please say exactly why you “can’t”.
Currently, it fails due to the “bad file descriptor” error.
Why the hell do you keep deleting the store?
Nikita Karetnikov nik...@karetnikov.org skribis:
Does the installation seem sane, basically? Do ‘guix build’, ‘guix
package’ etc. work somehow, or not even?
Turns out I can’t even build ‘hello’
Please say exactly why you “can’t”.
Currently, it fails due to the “bad file descriptor”
I’m attaching the version incorporating your suggestions, which was
tested with the empty store. There are a bunch of problems:
1. It doesn’t seem to prefetch all the needed dependencies. ‘guix build
hello’ (without network access) fails after prefetching the said
package.
2. The
Nikita Karetnikov nik...@karetnikov.org skribis:
1. ‘guix prefetch’ tries to configure and build some packages instead of
just downloading them. I tried the following on a machine with the
empty store:
a. Ran ‘guix prefetch hello’. Some packages were downloaded and
built (I
I forgot to comment on the actual patch...
Nikita Karetnikov nik...@karetnikov.org skribis:
+(define (fold-values f acc seen lst)
Use ‘fold2’ from (guix utils) instead.
+(define (derivations-to-prefetch store drv)
+ Return the list of fixed-output derivations that DRV depends on, directly
1. Should the recursion stop when ‘fixed-output-derivation?’ returns #t?
I think so. In general fixed-output derivations are the things you
would like to pre-fetch; so you would typically call ‘build-derivations’
on these to do the actual pre-fetching.
Could you show a package with a
Nikita Karetnikov nik...@karetnikov.org skribis:
1. Should the recursion stop when ‘fixed-output-derivation?’ returns #t?
I think so. In general fixed-output derivations are the things you
would like to pre-fetch; so you would typically call ‘build-derivations’
on these to do the actual
Nikita Karetnikov nik...@karetnikov.org skribis:
Is there a function that accepts a package name and returns a list of
implicit inputs?
No, because by definition, those “implicit inputs” are not listed in the
package object. Instead, they are added by the build system (see
Nikita Karetnikov nik...@karetnikov.org skribis:
The simplest way to do it would be by walking the package DAG: start
from ‘foo’, accumulate its ‘package-source’, then traverse its inputs,
etc. Recursion would stop at the implicit inputs (GCC, glibc,
Coreutils, etc.), though.
If you’d like
Is there a function that accepts a package name and returns a list of
implicit inputs?
No, because by definition, those “implicit inputs” are not listed in the
package object. Instead, they are added by the build system (see
build-system/gnu.scm.)
That’s why I suggested using derivations
Nikita Karetnikov nik...@karetnikov.org skribis:
By default, Guix fetches source tarballs on demand. You download a
tarball, configure and install, move to the next one, and so on. But it
may be useful to fetch all the prerequisites before building.
For instance, you travel frequently and
By default, Guix fetches source tarballs on demand. You download a
tarball, configure and install, move to the next one, and so on. But it
may be useful to fetch all the prerequisites before building.
For instance, you travel frequently and don’t usually have Internet
access. So it’d be nice
14 matches
Mail list logo
