• bamboo@lemm.ee
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    2 months ago

    This is the kind of crap that makes me glad flatpak and such exist. I don’t want a maintainer making arbitrary decisions like this, it adds unpredictability and platform inconsistency.

    A similar issue I face is that on Debian the python stdlib well… isn’t all standard. In particular they split off the venv package, and it’s an extra step that adds unnecessary complication. No other Linux distros or other OS do this, it’s so frustrating. I guess someone is super happy they saved a few hundreds kilobytes of disk space though.

    • moonpiedumplings@programming.dev
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      2 months ago

      I guess someone is super happy they saved a few hundreds kilobytes of disk space though.

      Yes. All the people basing docker images off if debian, and trying to get them as small as possible. The splitting up of packages, allows people to only pull in what they need.

      • 𝘋𝘪𝘳𝘬@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        If you base your Docker images on a full distribution then that is entirely your fault. People usually use specialized distributions for that.

        You could even bootstrap your needed tooling from Busybox.

        • bamboo@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          Debian or Ubuntu are usually the best choice if you depend on glibc. Alpine is definitely more compact but musl isn’t always an option.

        • lemmyvore@feddit.nl
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          Specialized distributions like minideb still use the Debian packages, they just use fewer by default.