Results 1 to 2 of 2
Many sites offer precompiled 3rd party rpms, that one can install on their linux distribution (such as package-1.0-1.packager.rpm). These sites also typically offer the source code (package-1.0-1.packager.src.rpm). Is it feasible, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-09-2005 #1
rebuild with rpm - advantages? disadvantages?
Is it feasible, and if feasible, is there any point in downloading the source code package with the rpm, and then rebuilding the source on one's pc, from the rpm? Is one better off going straight to a corresponding tarball?
The idea behind rebuilding would be to obtain better performance from a customised/optimised rpm, with less dependancy problems that would typically come with a tarball (?).
Please, what are the advantages and disadvantages of any such rebuilding?
And if useful, what are the custom rpm commands (and tips/tricks) that should be used if this is a good idea?
- 10-09-2005 #2
- Join Date
- Mar 2005
:: can optimize it for your box
:: don't have to worry about for example having a different version of a spesific library
:: can use source RPM's used to build binaries for other distros (usefull if they provide suse RPM's and source rpms only)
:: compile CAN fail
:: takes more time
:: if wrong cflags, the binary can be unstable/malfunctioning
I havent used RPM for ages, but I think it was something like rpm --rebuild package... Check the manpage, and type /source[enter] or something like that to search for "source".
This will be almost the same as compiling from a tarball, using checkinstall and taking care of the deps yourself, thought tarballs are usually newer, while source RPMs are probably tested on your distro.
those are what I can think of atm