• JamesBoeing737MAX@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Eh it’s kinda fine most of the time. But if you really don’t have time to fix dependencies (via dnf) and constantly leave it for later, many broken things accumulate. It’s usually fine (and usually works for at least a few years without problems, even on arch).

    Edit: also the other comments.

        • Jade@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          2 months ago

          The worst I’ve ever had happen could be fixed with the (prompted) --allow-erasing flag, and I messed around with additional repositories a lot

          • SlurpingPus@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 months ago

            messaged around with additional repositories a lot

            Gotta say again, as an APT user, I have no idea what “messaged around with additional repositories” means.

        • SlurpingPus@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 months ago

          Thanks again for the info. However, I can’t remember when I ever had to ‘fix dependency problems’ with APT. Maybe when I ran Debian Testing for a while, or if I added one too many external repos, or if I really really wanted to run two explicitly conflicting packages — but still it’s such a foreign thing that I can’t recall if it actually ever occurred. Apparently APT’s reputation for most solid dependency resolution among package managers is quite well deserved.