Using rpm to install sw locally on RHEL cluster [duplicate]

How can I install an RPM on a machine where I don't have root permissions? I want to install a package for my use only in a personal work directory. I'm running SuSe SLES10.

Please don't flame me with "This idea is so dumb, you shouldn't do it because all requests must go through the corporate root god, may he live forever."

I know I can request this of the root god, but I'll be shot down (for immaculate, impeccable reasons, I'm sure...). Besides, he'll never get around to installing it even if he does say he'll do it.

Solution 1:

cd my-dir;
rpm2cpio to-install.rpm | cpio -idv

See How To Extract an RPM Package Without Installing It (rpm extract command).

Solution 2:

How to extract rpm packages contents

export ins=foo-bar.rpm
rpm2cpio $ins | cpio -idv

How to extract tar.gz archive

gzip -dc foo-bar.tar.gz | tar xvf –
cd foo-bar-dir

How to extract tar.gz packages to the current directory

export file=foo-bar.tar.gz
# Note that `xovf` switch order *matters*
gzip -dc $file | tar -xovf -

How to build binaries as a non-root

./configure --prefix=$HOME && make && make install

Solution 3:

I think the "real" answer to "installing" an rpm without root privilege is, you can't. BUT assuming you could actually start the install process...

RPMs install using a list of instructions provided in a specification file (.spec) that usually follow the Filesystem Hierarchy. Most paths on that hierarchy are almost always operating system paths and not user paths. So unless your username has access to all of the paths an RPM installs to, then it would certainly fail. If you create an RPM that prefixes all of its paths with /home/me (or some other path you own), then it would work. This would require acquiring a src.rpm and extracting it as explained in other answers, then rebuilding it. By the time you do that, you might just consider getting root access or building the software from scratch (usually what you do if you do not plan on distributing the software across many machines).

There are clever tricks to help you in the manual build process. For example, you can utilize the dependencies already listed in an RPM to get all of your dependencies: https://stackoverflow.com/a/13877738/1236128.

Solution 4:

Another option is to install from source, where you can usually change the install directory using the --prefix switch.