I’ve been using paru. Just wanted to know if aura is, in your opinion, better than paru and why.

    • naeap@sopuli.xyz
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      24 days ago

      Hehe

      I’m using yay, because it was “the new thing”, when I switched to Arch (and Arch-based systems)

      But after that I’ve stopped comparing

      Is there anything new, that is actually worth switching from yay?

      • Kogasa@programming.dev
        link
        fedilink
        arrow-up
        15
        ·
        24 days ago

        Paru was at one point a rewrite of yay in Rust, and has since continued development as a pseudo parallel fork. It’s good. Dunno if it’s worth switching, you’d have to see if there’s any specific features you might happen to want, but they’re both fine

      • Lucy :3@feddit.org
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        edit-2
        24 days ago

        Maybe there’s builtin customizepkg or custom repo support in some helper?

  • shapis@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    23 days ago

    Never used aura but paru is great specially if you also install bat for colored PKGBUILDs.

    Makes reading them much easier. I never did before doing this.

  • przmk@sh.itjust.works
    link
    fedilink
    arrow-up
    4
    ·
    23 days ago

    I have decided against Aura because it splits the commands for AUR from the standard repos. With paru I can upgrade both by running just paru. In the end, that’s all I mostly do with an aur helper.

  • Kalcifer@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    24 days ago

    Honestly, from a day to day standpoint, by my experience of using both, there’s little practical difference between, for example, yay, and paru — it mostly just ends up coming down to subjective, nitpicky meta things about the program itself.

    Up until this post, I hadn’t heard of Aura, but, after briefly looking at its repo, it appears that it’s effectively the same as yay and paru [1.2]; what it tries to do differently is it tries to ensure that there are translations of it (I’m guessing its output) in other languages [1.1.1]. One thing that I’m knee-jerk not super fond of is that it utilizes its own centralized metadata server [1.1.2], though I admit that I haven’t thought about that a great deal, so perhaps there are some aspects that about it that I’m missing, or perhaps misunderstanding, or perhaps there’s a different way to view it.

    References
    1. README.md. fosskers/aura. GitHub. Accessed: 2024-11-03T05:53Z. https://github.com/fosskers/aura/blob/master/README.md.
      1. Section: “The Aura Philosophy”.
        1. Section: “Multilingualism”.

          […] From the beginning, Aura has been built with multiple-language support in mind […]

        2. Section: “Independence”.

          Aura has its own […] Metadata Server called the Faur. The Faur in particular helps reduce traffic to the main AUR server and allows us to provide unique package lookup schemes not otherwise available.

      2. Section: “What is Aura?”.

        Aura is a package manager for Arch Linux. Its original purpose was in supplementing Pacman to support the building of AUR packages […].