• j0rge@lemmy.ml
    4·
    2 months ago

    Because the image never gets built if there’s a packaging error, so the user never ends up on a broken image. A broken package never makes it to the end. If it’s broken the user just doesn’t get an image until the package is fixed and then they get a new image.

    • ranzispa@mander.xyz
      1·
      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
        3·
        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
          1·
          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.

            • ranzispa@mander.xyz
              1·
              2 months ago

              In normal repos they also test their packages. I do not think it is possible in any distribution repo to ship a binary which did not compile. Dynamic library linking may have some problems I guess, but unless you’re using arch that is generally never a real problem with package manager installations. I have never got a package which plain does not run.