• Ephera@lemmy.mlOP
    link
    fedilink
    English
    arrow-up
    4
    ·
    9 months ago

    You can’t tell that from the screenshot, but I can tell you that I took this screenshot on my Linux box, while upgrading my system packages as an end-user.

    I believe, the problem comes from a community repo I added, which doesn’t have to adhere to quite the same quality standards, but evidently they have some distinction between build envs and production envs, and well, I’m at least hoping that my laptop isn’t deemed a build env… 🙃

    • s12
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      Ah! So build implies non-production?

      • Ephera@lemmy.mlOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        9 months ago

        My usage of the word “production” was a bit non-standard here, in case that confuses you.

        Normally, it’s used for hosted services, where you have the three hosted environments “development”, “integration” and “production”.

        In this case, I’m guessing, it’s rather the case that they had a build configuration for running it in their “build-env”, so probably a CI/CD runner. And then there would be a different build configuration for when they’re creating a release distribution.

        In a very abstracted sense, the “production” environment is where you roll out your release distribution to, so if you will, my laptop is one of thousands of production environments for this application, but only tongue-in-cheek…