[SOLVED] VMWare View Client 2.2.0 with proprietary PCoIP extensions
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This post is something between a tutorial and a quest for not everything works yet. If you need the proprietary PCoIP extensions in the VMWare View client to connect to your corporate network, the open source client wont help. At the moment there is only a official Ubuntu package but no direct download from the website. But you can use the sources from the Ubuntu package to make a Slackware-Package.
There is only a i486 version of the binary, no 64-bit version. So if you are on a 64 bit system you need to make sure you set it up for multilib as explained here: http://www.slackware.com/~alien/multilib/
If you are 32-bit ready, download the tar from the Ubuntu launchpad here and place it in a empty folder you use to build the package.
This package basically contains all the files you need with the correct path except for the documentation. The followind SlackBuild script takes care of this problem. Just save the following script in the same folder as vmware-view-client.SlackBuild and run it as root to build the package:
Code:
#!/bin/sh -e
#Set initial variables:
CWD=$(pwd)
if [ "$TMP" = "" ]; then
TMP=/tmp
fi
VERSION=2.2.0
PKG_VERSION=2.2.0
APP=vmware-view-client
BUILD=${BUILD:-1_bk}
PKG=$TMP/package-$APP
set -e
rm -rf $PKG
mkdir -p $TMP $PKG
rm -rf $TMP/$APP-$VERSION
# Change to the TMP directory
cd $TMP || exit 1
# Extract the application source in TMP
# Note: if your application comes as a tar.bz2, you need tar -jxvf
tar -zxvf $CWD/$APP\_$VERSION.orig.tar.gz || exit 1
cd $APP-$VERSION || exit 1
chown -R root:root .
chmod -R u+w,go+r-w,a-s .
cp -r $CWD/$APP-$VERSION/* $PKG
mv $PKG/usr/share/doc $PKG/usr/doc
cat $CWD/$APP.SlackBuild > $PKG/usr/doc/$APP/$APP.SlackBuild || exit 1
# Create the ./install directory and copy the slack-desc into it
# mkdir -p $PKG/install
# cat $CWD/slack-desc > $PKG/install/slack-desc
# Build the package
cd $PKG
/sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH$BUILD.tgz
If the build is successful you just install the package as ususal:
Thanks schmatzler, this solved the problem. I couldn't find a settings.ini file on my system, though.
I edited the /etc/gtk-3.0/gtkrc file and added the line
Code:
gtk-fallback-icon-theme = gnome
which fixed the icons. Am I correct that if I want to add this setting to my SlackBuild, I would have to create a doinst.sh script which edits the above file as mentioned?
no, you should not edit files that belong to other packages if you want to publish your slackbuild script. Make a note in the README and let users do it manually
no, you should not edit files that belong to other packages if you want to publish your slackbuild script. Make a note in the README and let users do it manually
Ok, thanks. I think as soon as I find the time to write a README, I'll send the script to SlackBuilds.org.
please adjust the script with SBo templates as well before submitting
Thanks for the hint, I guess I would have forgotten to do this. There is no template for proprietary software (but if I understand correctly, it's ok to submit SlackBuilds for proprietary software as long as it's stated clearly in the README). I figure I just take the one that's closest to my script and modify it, right?
Yes, there are some packages which requires subscription and it's fine as long as it's stated in the README. All we provide is a script to package, not the real binaries
Yes, there are some packages which requires subscription and it's fine as long as it's stated in the README. All we provide is a script to package, not the real binaries
I just submitted a SlackBuild. I hope I haven't made any grave mistakes (guess there will be minor ones as it's my first SlackBuild ) Thanks for all the help.
Has anyone tried to install the 3.2.0 version that is downloadable from vmware.com?
I'm not able to connect using PCoIP and suspect it might be that I need a newer version.
Has anyone tried to install the 3.2.0 version that is downloadable from vmware.com?
I'm not able to connect using PCoIP and suspect it might be that I need a newer version.
I haven't tried yet. I don't like the installer, it replaces files from my package without warning. I think I'll try to install it manually.
Maybe it would be a good idea to open a new thread for this version where we can discuss the problems of this version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
) Thanks for all the help.
