Manjaro 2.0 Synopsis This document covers the organizational, technical, management, and other changes we (the Manjaro Team, et al) like to see applied to the Manjaro Project. The goal of this document is to serve as a point of discussion, and ultimately, once a consensus on its contents and written goals has been reached, as a guide for the organizational restructuring of the Manjaro Project. Motivation The Manjaro Project has been declining over the past decade. It managed to sustain a sizabl...
  • Veraxis@lemmy.worldEnglish
    1·
    7 hours ago

    Also, if a pkgbuild was updated for security reasons, now Manjaro is putting users at risk by continuing to serve the old version

    Hold up, isn’t that last point just a criticism of delayed updates in general? By that logic, would Manjaro be putting users at security risk by holding back the main packages?

    • teawrecks@sopuli.xyz
      1·
      1 hour ago

      The difference is they test the core packages they release. That’s their selling point. Just downloading old pkgbuilds without vetting anything is called an attack vector.

    • thevoidzero@lemmy.world
      1·
      2 hours ago

      Considering they just hold back packages, but do not do additional testing to release them, yeah, they should not do that.

      Arch already has testing repo, normal repo packages on arch are already stable enough