Re: patching binaries at install time without breaking rpm -V?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Christian Goetze <cg@xxxxxxxxxxx>:

Michael Jennings wrote:

[...] nuts [...]
If you can't fudge it with symlinks, use other software.  In any
event, this list is the wrong tree, and the barking should probably
stop.

Thanks for your helpful responses. If this attitude is representative of the list, then it goes a long way to explaining many of rpm's "features".

Actually, Michael gave you possibly very usable idea.  Usable depending on why
you need relocatable packages. For example, take Perl. There's /usr/lib/perl5 directory, location of which is hardcoded. So, you'd compile Perl telling it to
use /usr/lib/perl5-version (or whatever).

At the end of %install, rename /usr/lib/perl5-version to /usr/lib/perl5. Then,
in %post or %pre (doesn't really matter), create symbolic link
/usr/lib/perl5-version pointing to wherver the package is being installed. Yeah, you'll have one symbolic link created outside of new location, nothing is
perfect.

This scheme will work as long as you don't need more than one installation of
the exact same version of Perl, and all files are stored locally (no networked
file systems involved).  I've never played with relocatable packages, hower
something tells me RPM will not allow you to have same version of package
installed twice (or would it?).  So it might not be the problem anyhow...


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux