I think a Makefile would we useful, easy to read, instead of having different python scripts to write in different places on file system(s).
We could have in a single file: copy files to dest for install, remove for uninstall.
We could have different targets: install, start with enabling, uninstall, remove all, etc...
It is more compatible with "Unix/Linux" philosophy
Describe alternatives you've considered
Keep as it is.
Why I think having python scripts writing their own file(s) is wrong
Nobody can read/understand the python scripts, and where files are copied.
Python scripts do much more than they should (system admin is surely not a python task.
So I think: python is the driver, right. But sysadmin tasks should not be python. All files copy/removal and systemd management should be centralized in a Makefile.
I think a Makefile would we useful, easy to read, instead of having different python scripts to write in different places on file system(s).
We could have in a single file: copy files to dest for install, remove for uninstall.
We could have different targets: install, start with enabling, uninstall, remove all, etc...
It is more compatible with "Unix/Linux" philosophy
Describe alternatives you've considered Keep as it is.
Why I think having python scripts writing their own file(s) is wrong Nobody can read/understand the python scripts, and where files are copied. Python scripts do much more than they should (system admin is surely not a python task.
So I think: python is the driver, right. But sysadmin tasks should not be python. All files copy/removal and systemd management should be centralized in a Makefile.