In general, I consider Python to be not as problematic of a base dependency as
the dependencies for autotools, which are the following:
* bash
* m4
* perl (!!!)
* help2man
* make
* texinfo (!!!)
Now of course, most of this is hidden from you because autotools output is
stored in source tarballs released by projects (including rpm). In _that_
scenario, you just need POSIX shell, make, and libtool.
That said, if people _really_ think Python is a problem, I'm all in favor of
CMake here. The rest of the package manager stack maintained in this
organization uses it. Heck, openSUSE's Zypper uses it! Debian's apt uses it too
(they switched from their crazy half autotools half plain make system to CMake
~3 years ago).
The ergonomics of CMake are well-known at this point (thanks to KDE and
friends) and it's relatively trivial to bootstrap for builds. The portability
of CMake is so much better than Autotools as well. CMake is also highly well
supported in IDEs and text editors on all major platforms and several minor
ones.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1209#issuecomment-626266937
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
