AUR (en) - aura

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: aura 3.2.9-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/aura.git (read-only, click to copy)
Package Base:	aura
Description:	A secure package manager for Arch Linux and the AUR
Upstream URL:	https://github.com/fosskers/aura
Keywords:	AUR haskell pacman
Licenses:	GPL3
Conflicts:	aura-bin, aura-git
Submitter:	fosskers
Maintainer:	fosskers
Last Packager:	fosskers
Votes:	166
Popularity:	0.007145
First Submitted:	2012-06-13 09:49 (UTC)
Last Updated:	2022-05-23 18:42 (UTC)

Pinned Comments

fosskers commented on 2020-02-02 02:43 (UTC) (edited on 2020-05-27 18:08 (UTC) by fosskers)

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

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 38 Next › Last »

fosskers commented on 2014-07-21 18:54 (UTC)

@trusktr: 1. Yup, that can easily be included as an Arch Linux hook. 2. Can do, as a hook. Might be good to bring these points up here: https://github.com/aurapm/aura/issues/217

trusktr commented on 2014-07-21 18:37 (UTC)

Hi fosskers, If you could please make these two features take a prime seat in Aura 2, it'd be much appreciated: 1. Ability to edit all files in the tarball. 2. Keep build folders intact so when rebuilding a package that failed we don't have to wait another 2 hours to compile just to see if we have the same error or not. Add a -Ac (c for clean) option to delete build folders (or similar). If the build folder for a package already exists, ask the user if he wishes to start from scratch or use the existing files (e.g. the PKGBUILD might have been modified and the user might like to keep using it). These can be command line options. For example, --use-previous-build would make Aura use the stuff in the build folder, and without it aura will start over as normal. Interactive could be nice too. Either way.

fosskers commented on 2014-07-21 18:30 (UTC)

1.3.0.0 ------- - Last major version of Aura 1! We have entered the design phase for Aura 2, the implementation of which will transform Aura into a multi-distro package management platform. - Aura 1 itself has entered "legacy" mode. The only releases to be made on Aura 1 after this will be of `1.3.0.x`. You'll likely never see `1.3.1.x`. - Befitting a major release, we have: - New AUR interaction layer via the `aur` package. This fixes nasty "AUR lookup failed" errors. - `http-conduit` dropped for `wreq`, which is much easier to use. - Better version number parsing/comparison on installation/upgrading. - Package state backups have had their format changed. This BREAKS _all_ previously saved states. Please delete your old ones! - Implemented extended `--needed` functionality for the AUR side of Aura. AUR packages won't build if they're already installed. - Indonesian translations! - Other updated translations.

fosskers commented on 2014-05-15 19:23 (UTC)

Thanks, I've flagged the offending package as out-of-date.

thatch45 commented on 2014-05-15 19:03 (UTC)

I have been unable to install this because the dep haskell-blaze-builder seems to be broken.

purefn commented on 2014-05-07 20:19 (UTC)

By default a very general PKGBUILD will be created from the cabal file, but a patch can be created which will be applied to the PKGBUILD <https://github.com/magthe/cblrepo#adding-patches-for-packages> before any building is done.

fosskers commented on 2014-05-07 20:15 (UTC)

I will do that then. How do I ensure the PKGBUILD habs uses is (close to) the one aura uses now? There are certain directories aura touches (for backups, shell completions, etc) and there is very specific install behaviour in the current PKGBUILD. Hopefully they wouldn't just run `cabal2arch` on what's provided by Hackage, as that often produces overly general PKGBUILDs.

purefn commented on 2014-05-07 19:55 (UTC)

If aura was put on Hackage, then i686 and x86_64 would be created for it. Also, if you keep the version on Hackage up to date, the updates will get propagated to [haskell-core] when the cblrepo.db in habs is sync'd.

fosskers commented on 2014-05-07 19:29 (UTC)

So it seems [haskell-happstack] isn't needed at all anymore. That's great news! The wiki should be edited accordingly. Now, I don't see why aura couldn't be put on Hackage. People would probably feel better about installing `haskell-aura` from [haskell-core] than they would about installing `aura-bin` from here. Also, wouldn't that also generate an i686 binary as well? I'm sure a number of Aura's users would appreciate that.