Hey all,

I'm trying to create a package for the new version of the VMWare View PCoIP client. VMWare provides a installer which seems to have the locations (/usr/bin /usr/share ...) hardcoded or at least there is no documented way to specify the installation directory.

Now my question: Is there a tool or a way to force it to install to a certain directory which I then can use to create my package?

Thanks,

Beni

See "man chroot".

This was my first thought, too. But for some reason I can't get it to work. Maybe I'm too stupid for that, but I ran into the following problem:

One way is to copy my full base system to the directory I want to chroot to. This gives the installer all the dependencies it needs. But that's not practical because to build a package I need to remove them again afterwards and for a SlackBuild script basically copying the whole system is way overblown. I'm trying to find an easier way.

So I tryed to run to get chroot to run the installer in an empty directory, but this doesn't work. That's what I get:

The man page for chroot is very concise and doesn't really help.

The installer runs just fine without chroot. So it's not a 32 vs. 64bit problem. (The installer is a shell script with some binary data attached anyway.)

Extract the files out of the tar archive found within the self-installer

This will leave you will all the files in the "VMware-Horizon-Client-3.2.0-2331566.x86" directory. Now make your own installer!

You might also want to extract the script of the front of the bundle and open it in a text editor, to get some clues.

This is even integrated in the script and can be done via

But I wasn't able to figure out what I had to do to register a component with a install, just copying the files doesn't seem to do it. But maybe I really should dig into the script as you said. Guess there is no way around this.

Now that I've thought about it, chroot won't work here. The chroot environment won't point to any executables, like /bin/bash.

Listen to ruario instead of me.