Hi Alexis,
Alexis Simon <[email protected]> writes: > 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? Yes. The load path is going to end up with the files under your modules folder, so the module names do not change. > > 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`. Yes, but before you needed -L ., so there isn't really a change. > > 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. You can just do guix pull/time-machine directly, with local path to the channel instead of using the remote git repo. Regards Rutherther
