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.
p, li { white-space: pre-wrap; } I believe Linux folks can do better than this in explaining how to make Linux useful. From page 218 Chapter 18 Slackware Essentials followed by my attempts. (Most of the last 12 hours has been spent looking for an answer)
"# installpkg option package_name"
bash-4.1# installpkg -r opera
Cannot install -r: file not found
Cannot install opera: file not found
bash-4.1# installpkg -r /home/opera
Cannot install -r: file not found
Cannot install /home/opera: file not found
bash-4.1# installpkg -r /root/home/opera
Cannot install -r: file not found
Cannot install /root/home/opera: file not found
bash-4.1# installpkg -r opera-11.64-1403.i386.linux
Cannot install -r: file not found
Cannot install opera-11.64-1403.i386.linux: file not found
bash-4.1# installpkg -m opera-11.64-1403.i386.linux
Cannot install -m: file not found
Cannot install opera-11.64-1403.i386.linux: file not found
bash-4.1# installpkg -r /home/opera-11.64-1403.i386.linux
Cannot install -r: file not found
Cannot install /home/opera-11.64-1403.i386.linux: file not found
bash-4.1# installpkg -r file:///root/opera-11.64-1403.i386.linux.tar.xz
Cannot install -r: file not found
Cannot install file:///root/opera-11.64-1403.i386.linux.tar.xz: file not found
bash-4.1# installpkg /home/opera*
Cannot install /home/opera*: file not found
bash-4.1# installpkg /home/opera-11.64-11403.i386.linux.tar.xz
Cannot install /home/opera-11.64-11403.i386.linux.tar.xz: file not found
bash-4.1# installpkg /root/home/opera-11.64*
Cannot install /root/home/opera-11.64*: file not found
bash-4.1# installpkg /media/S13.37d6
Cannot install /media/S13.37d6: file not found
bash-4.1# installpkg /dev/sr0/media/S13.37d6
Cannot install /dev/sr0/media/S13.37d6: file not found
bash-4.1# installpkg /tempus/fugit
I do not know what happened to Chrome after I downloaded it, but I did find these three files in Home and I would like to know how to install them. Then I would like to install Slack's 13.37's Disks 5 & 6 which I purchased from Slackware along with the two Linux books. I could not find any answers in Linux: The Complete Reference either.
Well,
1) there are no -r or -m options for installpkg at present
2) the package name should be the full name of a Slackware package (usually ending in .tgz or .txz) and *not* a source tarball or an abbreviated name and should refer to a mounted directory (not to something in the /dev tree)
3) if the package in question is not in the working directory, the package name should include its full path.
To know more, type "man installpkg" in a terminal.
HTH
EDIT None of the 3 files you mentionned at the end of your post is a "Slackware package", they seem to be what is called a "source tarball" which can't be installed directly : first step should be to make (or build) a package of it. You will find instructions for that here.
The files provided in disks 5 & 6 are "source packages" (or tarballs) that you can't install as such. They are provided only to allow you to (edit the souce files in it if needed then) rebuild a package using the Slackbuilds provided as well.
Last edited by unSpawn; 05-30-2012 at 05:24 PM.
Reason: //Edited for Didier Spaier after 5 day edit limit
Elaborating a bit on Didier's reply, regarding these three package files:
You need to determine, first, the full pathnames of the files. If you see them when you run "ls", then you can make their full pathnames by taking the output of "pwd" (for instance, "/root") and the files' names. If they are in "/root", then your installpkg commands would look like this:
an easy way to make sure you have the correct pathnames of the files is to invoke "ls" on the pathnames, like so:
ls /root/opera-11.64-1403.i386.linux.tar.xz
If it says "No such file or directory", then the file is not in "/root" and you need to hunt around for it. If, instead, it shows you the pathname you typed in, then that's the right pathname to pass to installpkg.
To see the full pathnames of all of the files in your current directory, you can use the backtick ` around pwd to pass its output as a parameter to ls, like so (be mindful of the whitespace; there must be none between `pwd` and "/*"):
The packages you appear to be trying to install are not a native Slackware packages and hence cannot be installed in that way. To avoid further confusion it might be easier just to use native packages. It looks like you run 32-Bit Slackware.
(Note: I use "upgradepkg --install-new" here because if you did a full install it is likely you already have an older version of Firefox installed already)
Slackware does not handle software installation like any other distro. It does not resolve dependencies and it does not attempt to have a wide variety of "optional" packages in the official repos. Slackware's included software also tends to be a little behind the bleeding edge, because stability is a core Slackware feature.
For many of us, Slackbuilds.org is the go-to source for "unofficial" packages, but we still have to resolve dependencies.
As regards Opera, I have had good results downloading the *.tar.gz file from the Opera site, decompressing it, and running the install script which is included in the tarball. Indeed, in seven years of Slacking, that method has never failed me. But ruario is the Opera expert around here and I defer to him in all things Opera.
As regards Opera, I have had good results downloading the *.tar.gz file from the Opera site, decompressing it, and running the install script which is included in the tarball. Indeed, in seven years of Slacking, that method has never failed me. But ruario is the Opera expert around here and I defer to him in all things Opera.
Indeed that works just fine (on pretty much any distro). However since the OP appears to be relatively new to Slackware I thought it might be better for him to focus on understanding installation of native packages first and worry about non-native packages later. Hence why I provided the links.
How do I extract a package like it says to do in Step 1 HOW TO? And when I download a package which is the better deal: Save file or Open browse? (I googled the string, ""how to extract" Slackbuild pkg," and a little over 200,000 hits came up in under 0.4 seconds telling me something about .rar.)
Intuitively, the decision would be based for me on how much I have muddled the original Slack installment so I would trust it and go to "Save File." Based on what I have read here, I could assume that if I were in "root" then the working directory (root) is where I would find the file location after it downloaded.
By the way, Linux Commands by CheapBytes helped me understand pwd & ls a little better, so I got to thinking, "Does the explanation process for learning Linux via texts' Table of Contents and the command line follow the tree protocol or format of device, directory, folder, file, sub-file etc also to provide a dependable pattern for understanding?" (e.g. /root in the Table of Contents would be a chapter to explain what "kernel" means.)
Anyway, I stumbled onto http://commondatastorage.googleapis....25.142.tar.bz2 and copied it in the URL bar like the HOW TO instructed. It downloaded and I replaced the identical one already in /root/Home, but it has 0 bytes and the new one reads ...gz.part and is increasing in Megabytes as I type. Chromium.tar.gz did not seem to work. OK, something popped up and had "Activate" on it so I clicked it just now. It reads 166MB and the file which read 0 bytes disappeared.
Let's see. This is what I have to show for trying to download and install Chrome.
bash-4.1# ls ./root
Desktop chromium.tar.gz flashplayer-plugin-11.2.202.235-i386-1alien.txz opera-11.64-1403.i386.linux opera.tar.gz
Opera-Background-Clouds2.jpg firefox install_flash_player_11_linux.i386.tar.gz opera-11.64-1403.i386.linux.tar.xz
chromium-18.0.1025.142.tar.bz2 firefox-12.0.tar.bz2 mozilla-firefox-12.0-i486-1_slack13.37.txz opera-11.64-i686-1ro.txz
bash-4.1# installpkg /root/chromium-18.0.1025.142.tar.bz2
Cannot install /root/chromium-18.0.1025.142.tar.bz2: file does not end in .tgz, .tbz, .tlz, or .txz
bash-4.1# installpkg chmod +x chromium-18.0.1025.142.tar.bz2
Cannot install chmod: file not found
Cannot install +x: file not found
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg ./root/Home/chromium-18.0.1025.142.tar.bz
Cannot install ./root/Home/chromium-18.0.1025.142.tar.bz: file not found
bash-4.1# installpkg chromium-18.0.1025.142.tar.bz2
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg /root/please.dont.laugh.because.my.brain.hurts&will.try.to.go.over.this.again.
Thanks for the heads up. This is the site which makes more sense than the other one which had only builds for 64bit systems I found. My learning skills are more kinesthetic than abstract so I would climb the tree to find my relatives or creep out into the intersection at the red light of hope which never changes and gamble the blondes at the other three lights facing me would not copy my movements.
It is pretty slick how you got to the packages, Ruario, and I will be working some more on reverse "engineering" how you got to them to make it so easy to install Opera, the Firefox update (could not find FireFox in the Slackbuild site above BrianL focused me on), and the FireFox plugin. I will be going over what everyone here has shared to see how it works. Thanks Didier, brianL, ttk, ruario, and Mr. Bell. I found a local meetup last week and those who appeared made me feel comfortable I could learn Linux from scratch. There is another meetup.com group I hope to find and attend named SLUG. The bar is closing, the menudo was good, and with an Argentina cowboy yell, goodnight.
bash-4.1# installpkg /root/chromium-18.0.1025.142.tar.bz2
Cannot install /root/chromium-18.0.1025.142.tar.bz2: file does not end in .tgz, .tbz, .tlz, or .txz
bash-4.1# installpkg chmod +x chromium-18.0.1025.142.tar.bz2
Cannot install chmod: file not found
Cannot install +x: file not found
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg ./root/Home/chromium-18.0.1025.142.tar.bz
Cannot install ./root/Home/chromium-18.0.1025.142.tar.bz: file not found
bash-4.1# installpkg chromium-18.0.1025.142.tar.bz2
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg /root/please.dont.laugh.because.my.brain.hurts&will.try.to.go.over.this.again.
You are making the exact same mistake as you made last time. Not every file you download is a Slackware package. In the same way not every file you download is a Windows program or a Word document. Why did you think that chromium-18.0.1025.142.tar.bz2 is something you could install with installpkg? It isn't a Slackware package and you cannot install it this way.
If I were you, I would therefore start with the assumption that most random files you find are not Slackware packages. As a general rule Slackware packages tend to end with .tgz or .txz. It is also possible but relatively unlikely that they may end with the extensions .tbz and .tlz. The error message your received should have given you this clue, it stated "file does not end in .tgz, .tbz, .tlz, or .txz". Thus implying that it should have one of these extensions to be a Slackware package.
However even then, I think it is worth pointing out that not every single .tgz, .txz, .tbz or .tlz is a Slackware package. Unless you got them from a site that specifically mentions Slackware or another Slackware user pointed you to them, you should still assume they are not Slackware packages. I can also say with certainty that files that end with .tar, .tar.gz, .tar.xz, .tar.bz2 or .tar.lzma are never native Slackware packages and hence will never install with installpkg.
The best way to get Chromium would be to compile it from source using a SlackBuild script. However, at this stage (with no intended disrespect) I would personally advise you not to bother as I am fairly certain it is beyond your current level (though probably not your future level! ), given you have not yet even understood what a Slackware package is and using SlackBuilds is more complex than using binary packages. Given that you (apparently) have Firefox and Opera installed stick with one of them for now, whilst you better familiarise yourself with your new Operating System. Later when everything starts to make more sense you can consider installing Chromium.
Last edited by ruario; 05-29-2012 at 04:43 AM.
Reason: added quote, trie dto be less condescending ;)
Ah what the hell, I'll give you a quick run down on how to get (actually how to create) a Chromium Slackware package that you can install. Though personally I would still advise you to wait a bit before you went down this route. If the steps don't make sense to you then it probably means you are not ready yet. It would be better to come back to this when you understand the underlying concepts. If I am wrong and it seems to make sense to you, proceed right ahead.
The Chromium package you downloaded early is the "source" package for Chromium, which is different than a "Slackware" package. It would have to be built into a Slackware package before it could be installed with installpkg. However, as it states on the Chromium SlackBuilds page, Chromium requires (depends on) a package called libevent. For this reason libevent itself is also needs to be built first and installed before you can install Chromium.
To install libevent grab the relevant SlackBuild package and the source package:
Code:
cd /tmp
wget http://slackbuilds.org/slackbuilds/13.37/libraries/libevent.tar.gz
tar xf libevent.tar.gz
cd libevent
wget http://www.monkey.org/~provos/libevent-2.0.10-stable.tar.gz
Now switch to root via the su command:
Code:
su -
Now build the Slackware package:
Code:
cd /tmp/libevent
./libevent.SlackBuild
If this completed correctly then the line "Slackware package /tmp/libevent-2.0.10-i486-1_SBo.tgz created." would be printed and you could install the libevent Slackware package with the command:
Code:
installpkg /tmp/libevent-2.0.10-i486-1_SBo.tgz
Only once libevent is successfully installed you could then build the Chromium package and install it as follows:
Code:
cd /tmp
wget http://slackbuilds.org/slackbuilds/13.37/network/chromium.tar.gz
tar xf chromium.tar.gz
cd chromium
wget http://commondatastorage.googleapis.com/chromium-browser-official/chromium-18.0.1025.142.tar.bz2
If you are not already/still root, switch to root via the su command:
Code:
su -
Now build the Slackware package:
Code:
cd /tmp/chromium
./chromium.SlackBuild
If this completed correctly then the line "Slackware package /tmp/chromium-18.0.1025.142-i486-1_SBo.tgz created." would be printed and you could install the libevent Slackware package with the command:
Now (hopefully) you have Chromium installed. There are plenty of things that could have gone wrong however (like not having development tools installed, thus preventing package building)! If you get any error along the way, stop and post back here. Some kind soul might help you.
Last edited by ruario; 05-29-2012 at 03:26 PM.
Reason: switched examples to use: su -
It is pretty slick how you got to the packages, Ruario, and I will be working some more on reverse "engineering" how you got to them
I can tell you right now how I got to them.
The Firefox package was easy to find because Slackware includes Firefox, so any updates will be found in the "patches" directory on any of the Slackware mirrors. This is true for any other Slackware software that has security updates (they would be found in the same directory).
The Flash Plugin is not included in Slackware. These days the next port of call when looking for packages that aren't found in Slackware's own repository is http://www.slackbuilds.org/ (a.k.a SBo). However SBo does not host Slackware packages directly, rather it hosts SlackBuild scripts that create Slackware packages from "source" packages. Since using these scripts are more complex than using Slackware packages directly I decided not to give you to the link to the SlackBuild Flash Plugin page at that stage as it involved a little more work and explanation. Instead I looked in Eric Hameleers's package repository. Eric is a Slackware contributor and also maintains that nice repository of binary packages and SlackBuild scripts. His (binary) Slackware packages are trusted by the community and often more convenient (since no building is required). Hence I linked to his package.
For Opera, again SBo has a SlackBuild script. However, like with the Flash Plugin it would have been more complex to get you to use this to make your own package. Instead I linked to an Opera package I made myself. I work for Opera and host unofficial Opera Slackware packages as a convenience to Slackware users. Thus it wasn't that hard to find that one.
2) the package name should be the full name of a Slackware package (usually ending in tar.gz or tar .xz) and *not* a source tarball or an abbreviated name and should refer to a mounted directory (not to something in the /dev tree)
Pretty sure you meant usually ending in tgz or txz. I have never known a native Slackware package to end .tar.gz or .tar.xz. Unless the package ends with .tgz, .txz, .tbz or .tlz installpkg will return an error message stating, "Cannot install $package: file does not end in .tgz, .tbz, .tlz, or .txz".
These will all fail as they are not Slackware packages. Look at the endings. No Slackware packages end with .tar.xz, .tar.gz or .tar.bz2.
P.S. Whilst it doesn't have to be the case, "source" packages almost never use .tgz, .tbz, .tlz, or .txz but rather the long endings (.tar.gz, .tar.bz2, .tar.lzma, .tar.xz, etc.). So if a file is listed as being a Linux package and it has a long ending there is a fairly good chance it is a "source" package (an exception being ArchLinux and Crux packages, which end with either .pkg.tar.gz or .pkg.tar.xz).
Last edited by ruario; 05-29-2012 at 05:19 AM.
Reason: added more comments about extentions
Pretty sure you meant usually ending in tgz or txz. I have never known a native Slackware package to end .tar.gz or .tar.xz. Unless the package ends with .tgz, .txz, .tbz or .tlz installpkg will return an error message stating, "Cannot install $package: file does not end in .tgz, .tbz, .tlz, or .txz"..
Of course you are right, shame on me. I'll edit my previous post.
EDIT For some reason I don't see the "Edit" button on that post thus I can't correct it.
EDIT2 It seems that my previous post was too old to be edited by myself; hopefully a moderator nicely did it for me - thanks unSpawn
Last edited by Didier Spaier; 05-31-2012 at 02:49 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.