Upstream images vs bazzite:

  • ranzispa@mander.xyz
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    I had broken packages getting installed before. They would compile correctly but certain functionality would not work due to how it was packaged. This is not something which can be prevented, I do not believe it is possible.

    • j0rge@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      It is 100% possible and people have been doing it for years. If the package is broken the final product is never built, it’s impossible to ship it to the end user since it’s one whole complete image.

      • ranzispa@mander.xyz
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        I am afraid we are talking about different things. Recently I had to report a broken package to a repository. The problem was that they mapped a path to the incorrect directory.

        The software compiled and worked correctly, but some specific functionality which needed to read data from that directory was broken.

        I do not think there is a way to prevent this kind of errors.

        • ignominous_wombat@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          2 months ago

          I am thinking that they wouldn’t define that as a broken package, since I would consider that a bug that would need to be addressed in the next release. I would expect a broken package not to be able to run rather than simply to have a broken function.