How to figure out what packages are actually needed?

I have been running GNU/Linux as my primary for more than 2 years now, dual booting for more than twice that. I started out like most of those from my generation with ubuntu, but when 16.04 came out I started having a lot more stability problems than before, including a bug which caused completely random reboots with practically no clues in the logs. So I switched to Debian with gnome. Then I decided I didn't like gnome, and decided to go with i3. I've also played with arch a bit. The point is I've been around and I know what I want out of a system.

However, I've had some weird occurrences, like trying to set up sound in i3, or my printer working on an ubuntu system but not a debian one. So my question is, how do I determine exactly what packages my system requires to run smoothly? How do I pick out the few gnome and unity packages I need to use on a daily basis without installing/running their entire bloated systems?

Posted Jan 15, 2017, 2:09 AM UTC

43
TheBoxMage•

The thing about packages that are needed is that its very user dependant. If you're using i3 you can generally manage to avoid gnome and unity packages, but otherwise you just have to figure out what you need through either trial and error or careful planning.

3
smog_alado•

I don't think there is a hard and fast rule. But if you uninstall some packages, you can use apt autoremove to remove packages that you probably do not need anymore (packages that were originally installed because they were dependencies of something that you since uninstalled).

1
PipeItToDevNull•

I am running Manjaro and I am in the middle of trying to solve this problem, I found that you can use pacman -Qe to list packages explicitly installed, I am not sure what you are currently running though. My list is rather small (306 packages) that I have just been going through by hand

0