Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
10-31-2013, 12:32 AM
|
#1
|
Member
Registered: Mar 2012
Posts: 36
Rep: 
|
Where is it? Chromium Installation on Slackware 13.37 using SlackBuilds
Hello!
My name is Mark. I own a hand-me-down SONY vaio desktop that was new in ~2003. I am trying to re-purpose this machine to help me get through the next 18 months of school. I am certain it will serve all of my needs. I am running Slackware 13.37 with fluxbox for my window manager, and firefox as my browser. I am very happy with my setup but would like to install Chromium to see if google docs will meet my needs for some of my coursework.
Today I installed libevent and chromium (32 bit) on my computer explicitly following the instructions at SlackBuilds.org for my OS and hardware. Everything went flawlessly as far as I can tell. I periodically watched code flying by in xterm and received all of the messages saying everything was ok.
There's only one problem, and this is where I blush like a newbie.
Where is it and how do I launch it? As embarrassing as it is, I can't seem to find it and don't even really know where to look.
Please help!
Mark
|
|
|
10-31-2013, 12:46 AM
|
#2
|
Member
Registered: Aug 2012
Posts: 484
Rep: 
|
Hi Mark.
Try running this from a terminal (say xterm):
Code:
$ /usr/bin/chrome --enable-plugins
You'll have to add it to your fluxbox menu to have a direct launch method.
--mancha
|
|
|
10-31-2013, 12:48 AM
|
#3
|
Member
Registered: May 2008
Location: Republic of Texas
Posts: 393
Rep:
|
Look in /tmp ... ;-)
|
|
|
10-31-2013, 10:05 AM
|
#4
|
Member
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333
Rep:
|
Running the slackbuild will create a slackware package in /tmp that you can install with
Code:
installpkg /tmp/package-name
If you've done this, you can launch chrome by opening a command line and typing
|
|
|
10-31-2013, 09:57 PM
|
#5
|
Member
Registered: Mar 2012
Posts: 36
Original Poster
Rep: 
|
Hello!
Thank you for your help. Typing chrome launched the app just fine. Should I leave the application in /tmp, or do you recommend that I move it to some other directory. If so, is it a simple process of using basic command line commands to relocate it, or is a more complicated procedure required?
Thanks!
Mark
|
|
|
11-01-2013, 10:03 AM
|
#6
|
Member
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333
Rep:
|
The file in /tmp is not the actual application, it's a package that you used to install it. The actual application is probably /usr/bin/chrome (typing "which chrome" will tell you, if you're curious). So, you can actually delete the file in /tmp.
Basically:
- running the slackbuild script converts the source into a slackware package that's put into /tmp
- "installpkg /tmp/package-name" actually installs the package
- once this is successful, the source, slackbuild scripts and the package in /tmp are no longer needed
|
|
|
11-01-2013, 12:54 PM
|
#7
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,302
Rep: 
|
Quote:
Originally Posted by mattca
- once this is successful, the source, slackbuild scripts and the package in /tmp are no longer needed
|
But you can still save the package somewhere, so that if you decide to uninstall it, you won't have to rebuild it in case you change your mind. But don't let it in /tmp after installation, better move it, maybe to ~/packages, /home/packages, or on a removable device if you are short in hard disk space.
|
|
|
All times are GMT -5. The time now is 12:45 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|