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.
I am wondering what do you guys prefer when installing software. Slackware package or source code from the official website? I would like to know because sometimes if you want some specific functions you have to compile from the source code with specific parameters which Slackware package may not be provided.
For example, I just can't figure out how to install MPlayer from Slackware package. I can't get it done.
If you guys have any ideas, please drop me a line.
I nearly always compile from source. It's much easier to find the source, and compiling gives you 100% control.
I like the idea, but I'm hesitant to do more without having a good example of how to keep track of the versions, dependencies, and what needs to be upgraded with which packages.
For example, let's say that I install foo_1 which depended upon foo_2 and foo_3, and these were all installed from source. Not so hard to remember unless, like Okie, there are a significant number of these on your system. How does one best track all of these and thereby keep the system properly maintained?
It's the first thing I install after the base install is complete.
Sure, I've used that tool, and managing packages based on that method I certainly understand. I was just under the impression that the other posters I quoted were strictly installing from source, with no additional utilities that aided with managing the system packages. And if this were the case then I'd be interested in what method they do use for this function.
How do you determine which pkgs to upgrade and when to do so?
In short, how do you keep track of this setup?
when the author of the sourcode comes out with a new release i just delete the old installed package and compile the new one, a few times a week i just visit a few websites and take a quick peek at http://freshmeat.net/ once or twice a day,
the base system & Xorg is slackware - slapt-get updates that part,
Xian, make uninstall is something i never used, i usually just delete the executable from /usr/bin and check for any libs in /usr/lib and check for any directories in /usr/include & /usr/share
one other thing, this is just my personal home/office PC used just as a desktop/workstation and nothing running on it is absolutly crucial so if i mess it up i am only out a little time having to fix a few things or at worst having to reinstall the system, not like lives or business' are dependant on it...
i learned to be carefull about what i do so i do not spend all my time fixing things i broke, so if your carefull about what you do - you wont waste all your time fixing things that way you have more time to enjoy your PC productively...
I usually always use source, and then make a package for it. I currently have 100+mb of packages in ~/packages.
To do this all that is usually needed is.
1. Read documentation in tarball.
2. ./configure --help to find out all the additional options.
3. export CFLAGS="-O2 -march=i486 -mcpu=i686 -pipe";export CXXFLAGS="-O2 -march=i486 -mcpu=i686 -pipe" (editing them to whatever i need for that particular package.
4. ./configure --prefix=/usr --whatever-other-options
7 make DESTDIR=/work install
8. cd /work and then strip binaries, move/remove unnecessary/misplaced files, mkdir install, then add a slack-desc.
9. cd back into /work and do "makepkg programname-version-i686-1asw.tgz
Then i have a nice package that i can later remove/upgrade if needed. I can then do an rm -rf /work and i can remove the source code.
liquidtenmilion and all folks have given invaluable suggestions to me, thanks a lot.
liquidtenmilion,I personally prefer your option to make a slackware package because it's clear and intact if I want to remove/upgrade the package.However, can you point me to any website which you learned from regarding this package creation?
Okie, I have similar experience as you after compiled the source file if I want to delete them. But don't you think delete these files are difficult if you installed them from source files?Because it is not Windows,files are all kept in the Prgram Files by default. That's why I would like to ask the caption questions to see how you guys to deal with the package management. I do appreciate the advantages of using source files. However, I am more appreciative when I can manage my package systematically.
Thanks all you guys giving me many many good suggestions.