Hello everyone! It’s been about a month that I’m experimenting Debian on an external disk. For the most time, I’ve been using Testing. The issue is, that some packages are missing from Testing, while they exist on Stable (or on Unstable). The biggest problem with that is that some packages require dependencies that don’t exist on the Testing repo and as such I can’t install those apps.

So, I thought about adding the Stable repo, at a lower priority. If something doesn’t exist on Testing, it will grab it from Stable.

How bad is that approach? I’m not doing the reverse (using stable and grabbing apps from testing), which might be way worse. Does anyone else do that? I couldn’t find anything related online.

PS. I’m a bit tempted to switch to Unstable all together, but I don’t know if I’ll be careful enough to use it in the long run.

PPS. I might build a home nas at some point (with Debian Stable) and keep regular backups of my laptop so that I’ll be kinda safe if I ever switch to Unstable.

  • anamethatisnt@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    26 days ago

    Flatpaks share dependencies so after your first half dozen or so then the overhead for the rest isn’t very large. They simply reuse that 1+Gb you installed for the first batch.
    With that said, I also prefer native applications from a .deb or .rpm when possible and for no proper reason other than being used to doing it that way.