aur v3.0.0 Release Notes

Release Date: 2020-05-20 // almost 4 years ago
  • โž• Added

    • ๐Ÿ”ง Aura is now configurable via a conf file! Aura expects it at
      /etc/aura.conf, but will not break if it's missing. If you install Aura via
      ๐Ÿ“ฆ its AUR package, this file will be installed for you automatically.
    • A new top-level command: -P. This allows users to analyse PKGBUILD
      ๐Ÿ— files manually, as is usually done during building.

      • -Pf accepts a path to a PKGBUILD.
      • -Pd accepts a path to a directory containing a PKGBUILD.
      • -Pa to scan the PKGBUILDs of all locally installed AUR packages.
      • -P on its own will read from stdin. Combine this with -Ap to pull from the AUR:

      aura -Ap myget | aura -P

      sudo pacman -S aurvote
      

      aura >>= sudo indicates that someone may be trying to gain root access to your machine. aura >>= Potential PKGBUILD vulnerabilities detected.

    • ๐Ÿ— A new flag --vcspath to accompany the new VCS build behaviour (see below).

    • โช A new flag --allsourcepath to accompany the restored --allsource
      ๐Ÿ‘€ functionality (see below).

    • -O --adopt can now be called as -Oa.

    ๐Ÿ”„ Changed

    • VCS packages (e.g. *-git, *-svn, etc.) and their cloned sources are now
      ๐Ÿ— built and stored in /var/cache/aura/vcs. Subsequent builds will no longer
      ๐Ÿ‘ฏ reclone everything.
      #462
    • --hotedit will now offer to edit .install and .patch files. #208
    • ๐Ÿšš Some modules have been renamed and moved around.
    • Aura.Diff and Aura.Pkgbuild.Base have had their contents folded into other
      modules.

    ๐Ÿ›  Fixed

    • A regression that broke -Bc. #592
    • โช The functionality of --allsource has been restored. #538
    • A minor difference in the behaviour of -Ss relative to pacman. #599