> * Makes only sense to be installed using your distribution's package manager
Why? This is a requirement I don't understand.
That might be an overstatement. This is software to help install and configure other software, so it doesn't make sense if it has a complex installation procedure.
Of course, installing using pip from an URL is a simple installation procedure, so I could go for that.
> * Keep the packaging in the main source Git repo
The RPM packaging or the Python (pip/poetry packaging)?
The RPM packaging. I don't often see many examples of software which is package-friendly out there.
> * Is there any project out there with similar goals doing things "correctly" I could "copy"?
I don't know any Python project with automatic Copr builds from git, but maybe
look at a non-Python one?
https://copr.fedorainfracloud.org/coprs/dcantrell/rpminspect/package/rpminspect/
https://github.com/rpminspect/rpminspect/blob/master/.copr/Makefile
Oh, that's most useful, thanks!
> * pyproject-rpm-macros looks like something useful for what I want to do, can it be used on to package for EL8? (I only see Fedora branches)
It cannot. pyproject-rpm-macros heavaily relies on technology not yet (fully)
available in EPEL 8 which is unfortunately now an ancient distribution when it
comes to leading edge stuff :(
- RPM buildrequires generators are missing (old RPM)
- new Python RPM dependency generators would have to be backported
ideally with parametric generators from Fedora 33+'s RPM
- RHEL 8 has an ancient pip version 9, it might work,
however nobody was brave enough to try it)
- tox 3.13+ is needed (EPEL 8 has tox 3.4) for %tox
No worries, I just wanted to know if it was worth investigating that. Thanks!
I might for the moment make something pip-installable from a URL, so I have something "useful" as soon as possible, and postpone RPM packaging to after that.
Thanks!
Álex