[SOLVED] Cannot install wicd-1.7.0 in Slackware 13.0
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
(Background: my wireless worked fine for a long time using wicd-22.214.171.124 and then all networks became hidden. The wicd website said there was a bug in 126.96.36.199 and to upgrade.) I obtained wicd-1.7.0.tar.bz2 from sourceforge.net. Slackware man pages recommend "installpkg <name>". I did "removepkg wicd..." and then install. Installpkg said it could not install it because it did not end in .tgz,.tbz,.tlz, or .txz. I changed the name to wicd-1.7.0.tbz(assuming that was equivalent) and did installpkg again. That gave "Verifying..., Installing..., Warning: package has not been created with 'makepkg'. Package wicd-1.7.0.tbz installed."
There is no entry for it in the Kickoff Application Launcher. There is an entry for it in /var/log/packages. There is in /etc/rc.d./rc.wicd a script marked executable. Can anyone see what got lost?
Currently still unsolved. --Guanx, I am not sure of your first point. As to the second, the wicd site says that the Slackware 13.0 disk contains wicd 188.8.131.52 which has a bug and should be replaced, that being the unworking version I have. --Repo, slakfinder lists wicd 184.108.40.206, whereas the wicd site says 1.7.0 is the latest. Having the 1.7.0 tar.bz2, it seems I should be so close.
Currently still unsolved. --Guanx, I am not sure of your first point.
Simply renaming the file doesn't convert it's content into a Slackware package.
As to the second, the wicd site says that the Slackware 13.0 disk contains wicd 220.127.116.11 which has a bug and should be replaced, that being the unworking version I have. --Repo, slakfinder lists wicd 18.104.22.168, whereas the wicd site says 1.7.0 is the latest. Having the 1.7.0 tar.bz2, it seems I should be so close.
The "wicd.SlackBuild" file in slackware-dvd/extra/source/wicd shows how to make a Slackware package. You can just download the "slackware-dvd/extra/source/wicd" directory from slackware-current, which has wicd-1.7.0 and some patches.
[SOLVED]Guanx and Repo, you gave two other very good ways to get wicd-1.7.0 to Slackware 13.0, but I am embarrassed to say I was fiddling around with another way using the Slackware system itself, and thus being offline and missing them. For what it might be worth, this is what I did. Bunzip2 wicd-1.7.0.tar.bz2, giving wicd-1.7.0.tar. Untar that, giving wicd-1.7.0 files. The INSTALL text is scary, talking about all kinds of adjustments, but one needs only: "python setup.py configure","python setup.py install". Then I had to look for wicd (the user start program) in KDE Kickoff and click to set to the panel. Like everything else, it was easy if you did just the right thing. Thank you. (Note. For uninstalling, one may need to keep the tarball and unpack it again in the same directory.)