Hi, I'm packaging a Python application that doesn't have anything requiring compilation, it just needs copying files to the appropriate directories, so I started with the copy-build-system using an install-plan as follows:
~~~
(build-system copy-build-system)
(arguments
`(#:install-plan
`(("help/C/mazo" "share/help/C/")
("icons/mazo.svg" "share/icons/hicolor/scalable/apps/")
("mazo" "lib/python3.9/site-packages/") ; FIXME: Use GUIX_PYTHONPATH
("lugare.ulkeva.Mazo.desktop" "share/applications/")
("mazo.py" "bin/mazo")))) ; TODO: Make executable
;; TODO: Run tests.
~~~
This way, the package builds and I'm able to run the application in a guix
shell. However, as the comments above indicate, I'd like to
1. Indicate the destination for the "mazo" Python package using GUIX_PYTHONPATH
instead of the hardcoded path.
2. Make sure the "bin/mazo" file is executable (the source, "mazo.py", is
executable, though).
3. Run tests
Do you think I can achieve these sticking to the copy-build-system, or would it
be necessary to resort to meson or similar build systems?
Thanks in advance,
---
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/
publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
