On Dec 20, 2005, at 7:28 PM, Christian Goetze wrote:
How do people manufacture relocatable binary rpms when the binaries
in question have hardwired paths in them?
You don't.
You patch the binary to get the hardwired path into a config file,
then write the config file in a relocatable fashion.
Take, for example: perl. It is really unfortunate that all the
search paths for the built-in libraries are encoded as absolute
paths at compile time.PGSQL is the same way. The only way that
comes to mind is to ensure these paths to be reasonably long, then
to patch the binaries after installation to actually contain the
install-time paths. Unfortunately, this breaks "rpm -V" - for good
reason. Is there a way to invoke the signature step via the post-
install scriptlet? Or do people have better ideas on how to make
relocatable binary rpms?
I really wished that software writers would use the equivalent of
perl's FindBin construct to construct their internal search paths...
rpm isn't implemented in perl. Feel free to use perl and python and
ruby and whatever else you wish however.
73 de Jeff
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
