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
    25·
    9 days ago

    Interesting. As a former Manjaro user (several years ago now), my problems with the distro were more with their approach to package management and the AUR. They withhold packages for the main repositories, but the dependencies for AUR packages will always assume the latest packages, so I would constantly get into these dependency deadlocks where I could not install or could not update certain AUR packages because the necessary dependencies were the incorrect version. I view this as a fundamental technical problem with their approach, and was my main reason for switching away.

    Hopefully the new structure/leadership will result in technical changes which fix their issues. Though if I am being honest, the vision of a Manjaro with rolling packages is basically just a reskinned EndeavourOS, so I am not sure what they would need to do for me to recommend this distro to anyone.

    • Korkki@lemmy.mlOP
      6·
      9 days ago

      I just avoid the AUR on Manjaro whenever possible. It still works 99% of the time. The few things I actually need to be bleeding edge I will just try to build from source.

    • Giloron@programming.dev
      13·
      9 days ago

      The dependency issues seem like that are a flaw in the Arch design. It is the only package manager I’ve seen that requires running the latest available version of packages.

      • ShortN0te@lemmy.ml
        2·
        9 days ago

        Why should that be a flaw on Arch’s side, when it ooses no issue on Arch’s side? Partial updates are explicitly not supported. That would be fine for Manjaro if they would not encourage the use or for some cases even enable the use of AUR by default.

        • Giloron@programming.dev
          11·
          8 days ago

          Partial updates are explicitly not supported.

          This is what I’m referring to. Pacman is the only package manager I’ve used with this limitation.

          • ShortN0te@lemmy.ml
            1·
            8 days ago

            Yes but that is on Manjaro if they do not follow basic rules from their upstream and not on arch. If you ignore design desicions then thats on you.

              • ShortN0te@lemmy.ml
                2·
                8 days ago

                Thats the only (sane without tons of work) way how you can have a rolling release distro without the need to compile everything yourself, everytime. Dependency issues will occure when glibc gets updated (or any other library) and you only update some programms but not all, its possible that those programms work or not.