Dne čt 17. září 2020 Michael via tde-users napsal(a):
On Thursday 17 September 2020 01:25:04 am deloptes via
tde-users wrote:
J Leslie Turriff via tde-users wrote:
#2 debian packages don't help much on an
RPM-based system. :-)
then build RPM or isolate as suggested, so that you can manage the
installed software easier later (for example if you have to update)
I can't say why, but it was way easier in CentOS (RPM) than Ubuntu,
Devuan, MX (apt) to compile from source and keep it updated that way.
It wasn’t until I switched to non-systemd Debian derivatives that I ever
saw a need to build a package.
2 cents,
Michael
____________________________________________________
Once upon a time I used RedHat Linux (please do not confuse it with the
current RHEL). Starting with version 5.0 and ending with version 7.3. At
the time I was used to building and maintaining my own RPM packages.
Although the creation of the source package was at first glance easier than
for deb packages, building binary packages was always a big pain. Towards
the end I was happy when I could use apt-get for RPM.
I've been using Debian since version 3.0 and when I learned how to build
packages and use pbuilder, it was a huge relief and much easier work than
ever before with RPM. Some time ago I switched from pbuilder to schroot +
sbuild, but the principle remains the same and just as simple.
Conversely, when I needed to solve some problem with building an RPM
package, I tried to find some tool comparable to pbuilder (I found a
mock), but there was a lot of pain in the RPM package management tools.
From my point of view, the state is so unfinished, one project replaces
the other, so in the final they are all constantly "in development". I
considered the "most perfect" when I found instructions for building
"dnf"
from the source code, which stated to use "dnf build dnf". In fact, I did
not understand how anything "enterprise" can be based on such an unstable
state of basic package management tools.
Cheers
--
Slávek