Package Details: aura 3.2.6-1

Git Clone URL: (read-only, click to copy)
Package Base: aura
Description: A secure package manager for Arch Linux and the AUR
Upstream URL:
Keywords: AUR haskell pacman
Licenses: GPL3
Conflicts: aura-bin, aura-git
Submitter: fosskers
Maintainer: fosskers
Last Packager: fosskers
Votes: 157
Popularity: 1.63
First Submitted: 2012-06-13 09:49
Last Updated: 2021-09-18 05:58

Required by (1)

Sources (1)

Pinned Comments

fosskers commented on 2020-02-02 02:43

If you'd rather not deal with Haskell dependencies, a pre-built binary is available in the aura-bin package .

Latest Comments

1 2 3 4 5 6 ... Next › Last »

FabioLolix commented on 2021-04-05 19:20

Conflicts "aura-bin, aura-git" is not needed, are that packages that need to provide/conflicts aura

fosskers commented on 2020-06-05 14:40

@Ultimatespirit: Done.

Ultimatespirit commented on 2020-06-05 01:06

@fosskers: I'd recommend placing 'ghc' as an optional dependency if at all. From what I can tell when stack is installed normally before hand (i.e. you already have developed with haskell / using stack) the --system-ghc line will always work, even if you don't actually have a system ghc (which ghc supplies). That is, to my understanding having 'ghc' as a makedepends right now will force the installation of the ghc package, which you may not have despite having stack (all arch haskell packages are dynamically compiled for example, so in my case I use stack-static instead of 'ghc'), even if it may not be needed.

In the end stack downloading ghc or 'ghc' downloading ghc, both will download it if it isn't there, only difference being stack's download isn't as obviously seen as a package by pacman, so maybe including a print out saying how to remove that downloaded data by stack if you don't want to just remove the package altogether.

tl;dr: Having ghc as a hard dependency means it will be installed erroneously in setups where you already had stack installed, and worryingly may or may not make aura depend on dynamic libraries even if the user is using stack-static or similar tools to avoid that specific issue.

yochananmarqos commented on 2020-05-27 18:25

@fosskers: Oh, duh. I didn't notice you added that, neat. It builds faster with it, too.

fosskers commented on 2020-05-27 18:21

@yochananmarqos: Thanks I'll add backup to both this and aura-bin.

I added ghc as a dep here so that I could use --system-ghc in the stack build line. Should reduce the memory footprint.

yochananmarqos commented on 2020-05-27 18:17

@fosskers: We both forgot the backup() array for the conf file, I just added it.

Are you sure it needs ghc to build? stack depends on ghc-libs, I haven't had any issues.

fosskers commented on 2020-05-26 17:05

@Ultimatespirit Done! Thanks for the suggestion.

Ultimatespirit commented on 2020-05-25 08:22

Can the PKGBUILD be updated to makedepend upon 'stack' only? That way installations using 'stack-static' or presumably 'stack' should also work (I can confirm 'stack-static' working, having just done such an install just now).

fosskers commented on 2020-05-21 17:17

@yochananmarqos: I adapted your PKGBUILD and have released aura-3.0.0. Thank you!

fosskers commented on 2020-02-19 15:47

@yochananmarqos Nice! I was going to use stack in just such a way. Thanks, I'll test this myself and adopt it if everything works right.