SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I am attempting to install a Google Chrome Slackbuild on Slackware 14.
I tried to install a Chrome RPM from the official website to no avail, so now I am attempting the Slackbuild route.
It has been brought to my attention that Google Chrome has runtime dependencies on ORBit and GConf. So I am trying to install builds for those two.
I have successfully unpacked and installed ORBit2, using 'tar xzvf' and 'sudo ORBit2.SlackBuild'.
I attempted the same steps for GConf. But when I ran 'sudo GConf.SlackBuild', I got the error 'No package ORBit-2.0' found'.
Now, the problem is that I installed 'ORBit2', not 'ORBit-2.0'. My guess is that this naming discrepancy is the reason that I can't install GConf.
So how do I change the names so that GConf will install?
Konsole says I should "consider adjusting the PKG_CONFIG_PATH environmental variable if you installed software in a non-standard prefix". It also suggests that I can "set the environmental variables DEPENDENT_CFLAGS and DEPENDENT_LIBS" to avoid the need to call pkg-config.
But I am not sure how to do these things, or what they mean.
Again, how can I change ORBit2 to ORBit-2.0 so that I can install GConf?
If you are really running Slackware 14 you should already have GConf and Orbit installed.
Please read the Google Chrome README in Slackware 14's "extra" directory if you want to know how install Chrome and its dependency, the PAM library:
If you want an easy way to keep Chrome up to date, you can run this script from time to time. It'll check what is the latest stable version of Chrome is and compare it to the version you have installed. If your version is different (or you don't have Chrome installed) it will automatically download the new version and repack into Slackware format. Otherwise it will just report that you are up to date. As a bonus you can run the script as a regular user (since it is able to make valid Slackware packages with root owned files even when not run as root).
P.S. If you want the same for Opera or Firefox I have similar scripts for them. It may not be immediately obvious why I have a Firefox script given that Slackware ships Firefox and provides updates but it can be handy as you can use it to track ESR releases (set FFESR=y) or if there is a delay in Pat updating the regular build. All of these scripts are doing binary repacks, not building from source. This has the advantage of being very fast and meaning you can take advantage of compilation optimisations that the upstream browser makers employ, e.g. PGO.
firefox in slackware64 is built with PGO too since january (and the slackbuild supports building of esr releases)
Still I can instant upgrade as soon as the update is available, with no delay waiting for packages from Pat. Also no need to 'build' Slackbuilds.org ESR with PGO, which would use a lot of time and resources. Mozilla already provide nice "official" binaries. I'd prefer just use them and get instant upgrades (SBo is currently 4 versions back 17.0.1 instead of 17.0.5 meaning it is lacking security fixes).
The other benefit is that the script not only automatically downloads the binary and makes the Slackware packages, it does the checking for updates and it'll do all this without having to be root. You only need to switch to root to install any packages that were made, if updates are found.
Last edited by ruario; 04-23-2013 at 04:16 PM.
Reason: added comment about old ESR on SBo
Yes, I know I could tweak the version of the SlackBuild on ESR but this is manual. Additionally as previously stated it is resource and time consuming to compile Firefox ESR with PGO, it is far quicker and easier to repackage the binaries. And it is easier with the script to keep track of updates.