On 06/12/2020 22.00, J Leslie Turriff wrote:
On 2020-12-06 06:16:21 Carlos E. R. wrote:
...
But I don't, ever.
The goal of using "checkinstall" is not to publish rpms, but to run "make install" and produce an rpm in/for my machine, and install that one instead, so that the rpm database knows that the package is installed, and so doesn't insist in installing the published package if it exists. And also facilitates uninstalling the produced package easily, because many devs create the "make install" procedure and forget about "make uninstall".
The instant one wants to publish the rpm, the road changes and OBS becomes the correct way.
In fact, I have something installed in my machine using "make install" because I could not find checkinstall. I forget which thing,
Hm. I would never have guessed that "checkinstall" is a tool for converting a tarball to an RPM. This is the sort of thing that drives me crazy: "I've got a great idea for a helpful tool! What should I call it? 'tar2rpm'? No, too obvious..."
No, it does not "convert". It runs "make install" on the directory you tell it (the current directory?), and basically captures what files it creates. With that information, it creates an rpm. It "checks" the "install" phase :-) Previous to that, you have to do "./configure" and "make" the project on your own. For example, looking at my ancient notes, I would do, as user: sudo /usr/sbin/checkinstall --arch=i686 \ --pkgname=geda --pkggroup=Compilaciones/Engineering/gEDA \ --pkgaltsource=www.geda.seul.org 'CFLAGS="-O2 \ -march=pentium4" make install' or sudo /usr/sbin/checkinstall --arch=i686 \ --pkggroup=Compilaciones/edit \ --pkgaltsource=http://www.lyx.org/ This is ancient stuff :-) Last time I used it was Aug 23 2012 -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)