Arch Linux

7761 readers

8 users here now

The beloved lightweight distro

founded 4 years ago

MODERATORS

k_o_t@lemmy.ml

Dependency cycle on Arch (btw) (lemmy.ml)

submitted 3 weeks ago* (last edited 3 weeks ago) by kixik@lemmy.ml to c/archlinux@lemmy.ml

2 comments fedilink hide all child comments

cross-posted from: https://lemmy.ml/post/21673875

Cross posting so that the OP realizes this community is alive. I have no issues with qemu, which is installed on my system with no issues.

Posting here as there doesn't seem to be an active Arch Linux community.

I noticed while updating my system today that I have a bunch of qemu packages I don't recall installing. So I took a look at why they were there and found this:
Name            : qemu-base
Required By     : qemu-desktop
Install Reason  : Installed as a dependency for another package

Name            : qemu-desktop
Required By     : None
Optional For    : qemu-base
Install Reason  : Installed as a dependency for another package
It seems like qemu-desktop was a dependency for something I later removed and pulled in qemu-base. However, because of the dependency cycle, they aren't showing up as orphans and has just been hanging around in my system along with 150mb of other dependencies.

Correct?

Edit: Adding clarification on why this was cross posted, and no I'm not the OP.

you are viewing a single comment's thread
view the rest of the comments

[–] UnfortunateShort@lemmy.world 2 points 3 weeks ago

That is mostly correct, although this is not a true cycle, since you can find packages that are strictly optional depencies, i.e. not a hard requirement for anything.