Ask Linux

107 readers

5 users here now

Ask the community any questions about Linux

founded 1 year ago

MODERATORS

voracread@lemmy.world

Dependencies - why does a package installed later become un-removable without nuking the whole system? (lemmy.world)

submitted 1 month ago* (last edited 1 month ago) by voracread@lemmy.world to c/asklinux@lemmy.world

2 comments fedilink hide all child comments

At times a package I install later on wants to take packages previously installed while going out. Some even try to take out core system packages. This mean trying out something is fraught with risk of permanently staining the installation.

Why does this happen?

top 2 comments

sorted by: hot top controversial new old

[–] JASN_DE@feddit.org 4 points 1 month ago (1 children)

Which distro? Which package manager? How do you remove them?

There are often options to remove a package with all its dependencies. If you hit that, depending on the package it'll try to remove half the system.

[–] voracread@lemmy.world 1 points 1 month ago

This was noticed in PCLinuxOS which has been my primary OS for many years now. This not from today so I do not have specifics here. The thought just popped in my mind after watching some video on YouTube.

Synaptic is the package manager front end for apt4rpm (I think)