you are viewing a single comment's thread
view the rest of the comments
[–] 41 points 7 months ago* (last edited 7 months ago) (17 children)

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.

  • source
  • hideshow 17 child comments
  • [–] [S] 8 points 7 months ago (9 children)

    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.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 12 points 7 months ago (8 children)

    IMO they should have made this the official policy instead of adding optional support for the AUR in pamac.

    At the end of the day, the AUR is just a pastebin full of pkgbuild files for people who know what they're doing. And as a distro aimed more at the average Linux user, rawdogging the AUR probably just shouldn't be part of the equation.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 2 points 7 months ago (4 children)

    Could they not have created an AUR mirror and delayed that to be in sync with the main repo's? It would have solved the AUR ddos that the Arch team got mad about a few times and the out of sync dependencies.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 7 months ago (3 children)

    The AUR just hosts pkgbuild files, no source or built packages. The pkgbuild can point to arbitrary external sources that could update separately. Manjaro could have their own AUR that hosts old pkgbuilds, but that wouldn't be foolproof since the external sources could change. Also, if a pkgbuild was updated for security reasons, now Manjaro is putting users at risk by continuing to serve the old version, and now that's another problem for them to solve.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 7 months ago (2 children)

    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?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 7 months 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

  • source
  • parent
  • [–] 1 point 7 months ago (2 children)

    It optional, for power users. That the point.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 7 months ago (6 children)

    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.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 6 points 7 months ago (5 children)

    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.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 7 months ago (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 7 months ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 7 months ago (2 children)

    True, but also why is that a rule from upstream?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 7 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment