Hi,
Thanks Ludovic for the answer.
I'm still not really sold on either solution, i.e. yours and Romain
Garbage's one where I just remove the .scm extensions from files I don't
want included.
When using my channel externally, would imports still look like
(use-modules (guix-tsverse packages foo)) in your use case?
I do not use emacs/geiser but I have the same question, when testing
packages now I'd need to use `guix build -L ./modules foo`.
Maybe a third question slightly related to channel building, how do
people usually test channel derivation building before pushing some changes?
I know how to build individual packages (cf above) but how does one do
the equivalent of a guix pull locally to test if the derivation is ok?
I often end up having to commit and push changes to the remote and then
guix pull to realize there is a mistake.
Best,
Alexis
On 26/04/2025 15:32, Tomas Volf wrote:
Ludovic Courtès <l...@gnu.org> writes:
You don’t have to rename the modules. Instead, you could do:
mkdir modules
git mv guix-tsverse modules/
and add (directory "modules") to ‘.guix-channel’.
That way, the modules would still have the same name as now, but they’d
live under modules/.
And I guess for Geiser you would then set geiser-repl-add-project-paths
to '("modules") in .dir-locals.el? Or do you have different approach
for this?
Tomas
