Re: Packaging Grip
Hi,
The Style Guide for Packaging Python Libraries[1] states that in cases
like this, one should package the library for both Python 2 and 3,
creating a third package that contains the executable. As this package
is indeed intended to be used as a CLI application (as its description
says), I've followed the examples found in packages like python-django
and tox and:
- Didn't used the application layout which stores files in
"/usr/share/", as it has modules that needs to be imported later;
- Removed the entry point script that is automatically created;
- Added a custom and simple script[2] that imports and calls Grip's
main function;
- Ended up with a single package called "grip".
As I said, I didn't invented this and followed the practices that are
being used by bigger Python packages. I'm entirely open about
discussing those decisions with my future sponsor in the RFS that I'll
be filling later today.
Regards,
Tiago.
[1]: https://wiki.debian.org/Python/LibraryStyleGuide#Executables_and_library_packages
[2]: https://github.com/myhro/deb-grip/blob/0fc1143/debian/bin/grip
--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil
Reply to: