Hi Untrusem,
Untrusem <[email protected]> writes:
So I use a refurbished T480 thinkpad as my machine and when I
want to
contribute to guix. I open a guix shell in my guix local
checkout
` guix shell -D guix git-absorb -m manifest.scm --pure `
As it takes around 40 mins to build scheme bytecode files, I
don't do
that and this makes feedback loop hella slow.
Are you using plain `make'? I use `make -j8' on hardware of a
similar
vintage, and while it is not fast, it takes around half the time
you’re seeing.
Every guix command `import, build, shell` will take around
10mins just
to first find the <package,file> and then start the operation.
for instance, `./pre-inst-env guix import -i <some file> go -r
<some-package>` would
take over 20 mins or more depending on the package, it doesn't
even
matter if you use `-e "(@@ (gnu packages <file>) <package>)"` to
pinpoint stuff while building.
This makes it really hard to do actually do something because
you would
have to run the command again even if you made a typo error, its
frustrating.
As Gabor mentions, you really do need to `make' before doing
anything.
It’s slow, but it’s slow once, instead of for every command.
My main issue is one Gabor also mentions, when switching branches,
file times are changed, and many files need to be recompiled
unnecessarily. The git-restore-mtime program seems like it’d be a
great help, and I may look into hacking on it, so it doesn’t touch
files which have local modifications.
-- Ian
