Hello, Karel Kočí <[email protected]> writes:
> I am pretty new to Guix, but I tackled this as well and ended up using
> time-machine. My issue was that I needed to check if the whole channel
> actually
> compiles when put together. I ended up with something like this in the CI:
>
> cat >channels.scm <<EOF
> (list
> %default-guix-channel
> (channel
> (name 'elektroline)
> (url "${CI_PROJECT_DIR}")
> (branch "${CI_COMMIT_BRANCH}")
> (commit "${CI_COMMIT_SHA}")))
> EOF
> guix time-machine -C channels.scm -- describe
>
> This will include dependent channels as configured in the current
> channel.
Hm, this is a nice trick, I will borrow it for our CI at $DAYJOB.
>
> I am not sure if this is the best way, but it worked for my use case.
Sadly it does not address the issue I am trying to solve for my personal
channel. I want to place .go files with the compiled code into the
repository itself, as a way to suppress following warning:
--8<---------------cut here---------------start------------->8---
$ GUILE_AUTO_COMPILE=0 guix repl -L. wolfsden/packages/golang-apps.scm
;;; note: source file ./wolfsden/packages.scm
;;; newer than compiled
/gnu/store/9r3a5hhl2y7k5h407fygb2vprif2jnb8-wolfsden/lib/guile/3.0/site-ccache/wolfsden/packages.go
--8<---------------cut here---------------end--------------->8---
They are annoying and add zero value. But as said before, I cannot
figure out how to produce said .go files.
Diky,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
