<ng0>the tracker can be searched, in the text files it is just "noise" in the code, you will only see it once you search for it. With the tracker you know directly which package has open tasks without searching explicitly for the kind of open task and directory
<ng0>sometimes the notes are okay, as they are right in place, but you get no central place for information
<ng0>no, they are always okay the problem is just that you don't know what exists.
<ng0>does someone of you keep their Shepherd user-services, for shepherd running on non-GuixSD systems, online somewhere? I need a practical set of examples to see how exactly they differ.
<ng0>I have a rather stupid question about the guix system disk-image command. I have read most of the code around it. We do not auto-compile the gnu/system/install.scm module, we just use it as an argument. So far I just assumed this only works when you are in the root of the git checkout out the guix source. I think I still don't understand the full PATH perspective. Will it work when I move elsewhere? Do I have
<ng0>to have the git checkoutout or is the location of the file in some environment variable and we could move whereever and it'd still be functional? Any further modules I should read to unerstand it?
<ng0>For a guix package definition I have which is using git: is there an easy way to have (dirname (current-filename)) point to ../../.. ? Whe I use (define %source-dir (dirname "../../../README")) I get an illegal filename message when I try to build, while in the repl I get returned "../../.."
<ng0>I have to instruct the source that 1. the source is at ../../.. so that not just the cwd is copied to the build machine, and 2. that the build happens at ../../..
<cbaines>ng0, try using the canonicalize-path function, in place of dirname
<ng0>I could chdir and then getcwd.. maybe that helps