28.04.2025 10:43:29 CEST Alexis Simon: > 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? >
The (directory) object in the channel definition defines the root of the Guile module path. [1] This is my third attempt to write a response to your question. I had confused myself, thinking I use the (directory) object, while in fact I do not. At this point I will just say this: keep it simple. Add the (object "guix-tsverse") line and push to the channel repository. If it fails to pull, create a "guix-tsverse" subdirectory and move "packages" into it. That would result something like: guix-tsverse/guix-tsverse/packages/* .guix-aruthorizations .guix-channel tsverse-manifest.scm tsverse-channels.scm [1]: https://guix.gnu.org/manual/en/html_node/Package-Modules-in-a-Sub_002ddirectory.html
signature.asc
Description: This is a digitally signed message part.
