Hi Ludo, >> For debugging package definitions, it would be really nice to be able >> to build a package from a checkout of the original project source >> code, rather than having to make a tarball for each modification of >> that source code. Is this possible somehow? > > You should be able to use “guix build foo --with-source=./foo” (note > that the directory name must match the package name). > > > https://www.gnu.org/software/guix/manual/html_node/Package-Transformation-Options.html
The name matching condition is my problem with this approach, which is why I was looking for a way to do specify a local source in the package definition itself. I am working in the Python universe where package names almost never match the name of the checkout directory because of the python- prefix. Moreover, I want to build both python- and python2- packages from my checkout. >> The manual suggests that a package source could be something else than >> an origin object, such as a local-file, but I cannot get even >> local-file to work. > > It should work (you must import (guix gexp) to get ‘local-file’). > > Can you share what errors you got? None - once I import (guix gexp) ;-) Thanks, Konrad.
