Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Hi
I recently read in the " Ubuntu Linux Bible" the chapter about Synaptic Package Manager. I understood why one would use SPM. However SPM doesn't automatically remove packages if I understand correctly; and being so that it doesn't:
I think the OP is trying to decide whether package management should be handled through apt-get commands or through synaptic. Not whether apt-get (install|remove) is appropriate.
To be honest, the man page for synaptic says:
Code:
NAME
synaptic - graphical management of software packages
SYNOPSIS
synaptic [options]
DESCRIPTION
Synaptic is a frontend for the apt package managent system. It allows you to perform
all actions of the command line tool apt-get in a graphical environemnt. This includes
installing, upgrading, downgrading and removing of single packages or even upgrading
your whole system.
A manual with detailed instructions can be found in the help menu of Synaptic.
From the description, synaptic is just a frontend to apt-get. In other words, all synaptic does is convert your mouse clicks to the appropriate apt-get commands. So they should be identical.
EDIT:
When you say "SPM doesn't automatically remove packages" it may be that synaptic can autoremove, but you may not have encountered the option/config setting on how to do so. I don't use synaptic that often. So unfortunately, I can't say "yes, go here" or "no, it doesn't". Though, again, according to the synaptic man page, the implication is that you can "perform all actions of the command line tool apt-get in a graphical environemnt."
Last edited by Dark_Helmet; 01-15-2012 at 12:04 AM.
In my case it just depends on where I am and how I feel. If I already have a terminal open I will use apt. If I have my hand on the mouse I'll use synaptic. End result is the same.
I think the OP is trying to decide whether package management should be handled through apt-get commands or through synaptic. Not whether apt-get (install|remove) is appropriate.
To be honest, the man page for synaptic says:
Code:
NAME
synaptic - graphical management of software packages
SYNOPSIS
synaptic [options]
DESCRIPTION
Synaptic is a frontend for the apt package managent system. It allows you to perform
all actions of the command line tool apt-get in a graphical environemnt. This includes
installing, upgrading, downgrading and removing of single packages or even upgrading
your whole system.
A manual with detailed instructions can be found in the help menu of Synaptic.
From the description, synaptic is just a frontend to apt-get. In other words, all synaptic does is convert your mouse clicks to the appropriate apt-get commands. So they should be identical.
EDIT:
When you say "SPM doesn't automatically remove packages" it may be that synaptic can autoremove, but you may not have encountered the option/config setting on how to do so. I don't use synaptic that often. So unfortunately, I can't say "yes, go here" or "no, it doesn't". Though, again, according to the synaptic man page, the implication is that you can "perform all actions of the command line tool apt-get in a graphical environemnt."
I think the OP is trying to decide whether package management should be handled through apt-get commands or through synaptic. Not whether apt-get (install|remove) is appropriate.
To be honest, the man page for synaptic says:
Code:
NAME
synaptic - graphical management of software packages
SYNOPSIS
synaptic [options]
DESCRIPTION
Synaptic is a frontend for the apt package managent system. It allows you to perform
all actions of the command line tool apt-get in a graphical environemnt. This includes
installing, upgrading, downgrading and removing of single packages or even upgrading
your whole system.
A manual with detailed instructions can be found in the help menu of Synaptic.
From the description, synaptic is just a frontend to apt-get. In other words, all synaptic does is convert your mouse clicks to the appropriate apt-get commands. So they should be identical.
EDIT:
When you say "SPM doesn't automatically remove packages" it may be that synaptic can autoremove, but you may not have encountered the option/config setting on how to do so. I don't use synaptic that often. So unfortunately, I can't say "yes, go here" or "no, it doesn't". Though, again, according to the synaptic man page, the implication is that you can "perform all actions of the command line tool apt-get in a graphical environemnt."
It is clear to me the "implication" So I'm thinking like "Roken" said: it just depends on where your at and what you might be doing that brings you to your decision as to weather opening a terminal is appropriate/suiting or use the SPM program to perform the desired task.
I tend to learn from example so here's a for instance ex
I recently installed Avast for my Linux/Ubuntu OS and I used SPM to install it.
(That was a troubleshooting situation all of it's own before SPM did it's job)
Would the other option of been to use apt-get; thru use of the terminal?... (to successfully install that program that I downloaded )
I appreciate all the help and understanding I am given-
Afterall, no one is going to maintain my Linux machine for me-
I tend to learn from example so here's a for instance ex
I recently installed Avast for my Linux/Ubuntu OS and I used SPM to install it.
(That was a troubleshooting situation all of it's own before SPM did it's job)
Would the other option of been to use apt-get; thru use of the terminal?... (to successfully install that program that I downloaded )
I appreciate all the help and understanding I am given-
Afterall, no one is going to maintain my Linux machine for me-
I do not know what instructions you followed to install Avast or steps you could have taken to avoid your "troubleshooting situation." If it was a .deb file you downloaded from some website (not from the Ubuntu repositories) then you can typically use dpkg for example:
Code:
sudo dpkg -i avast.deb
All of this information is officially documented here:
I do not know what instructions you followed to install Avast or steps you could have taken to avoid your "troubleshooting situation." If it was a .deb file you downloaded from some website (not from the Ubuntu repositories) then you can typically use dpkg for example:
Code:
sudo dpkg -i avast.deb
All of this information is officially documented here:
For a .deb file use dpkg (or double click it for a nice gdebi interface if you like GUI). At the end of the day, teh GUI is just a front for the terminal, and does exactly the same job. Reasons to use the terminal instead include:
i. It's faster (once you get used to it)
ii.If anything goes wrong, the terminal is more informative about why.
dpkg is the low-level tool that the system uses to manipulate individual .deb files, installing/removing, etc. You use dpkg when you need to install packages that aren't supplied through your system's repositories.
apt is a higher-level system that keeps track of all the .deb packages installed on your system, handles conflicts and dependencies, and lets you install from online (and offline) repositories. It calls on dpkg to do the actual package work.
Everything else is a front-end for and/or expansion to apt. aptitude, for example, is a cli package manager that provides a curses-based interface, and what some people say is better dependency tracking than the straight apt (and so it's not recommended to mix apt and aptitude).
synaptic and other programs are similarly gui front-ends. I don't know how much actual package tracking synaptic does itself though. I don't think it's much, if any, as I regularly use both it and apt, and have almost not problems between them.
The worst thing I've found that happens is that occasionally there will be some problem with broken packages that cannot be solved through the synaptic interface, in which case you MUST drop back into the shell and use apt to resolve it.
Note that gui package managers can often also be configured to work with other back-ends as well, such as on .rpm-based distros.
I feel much more educated now and less likely to make a mistake with installing pkg's.
As a newbie it is very important to me to learn and understand principles, correct practices and commands. Afterall no one is going to do it for me and maintaining my Linux machine is my responsibility. You didn't have to write to me....THANK YOU!
By the way, I'm starting to enjoy as I gain more knowledge and things fall into place and make more sense.
Now I'm reading and learning about :
-getting the latest stable release of the kernel ( just learning not doing)
-formatting a partition
upgrading to the next U.E.2.9 (U.E. 3.0 just came out)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.