Package Details: aura 4.0.8-1

Git Clone URL: https://aur.archlinux.org/aura.git (read-only, click to copy)
Package Base: aura
Description: A package manager for Arch Linux and its AUR
Upstream URL: https://github.com/fosskers/aura
Keywords: AUR pacman rust
Licenses: GPL-3.0-or-later
Conflicts: aura-bin, aura-git, aura3-bin
Submitter: fosskers
Maintainer: fosskers
Last Packager: fosskers
Votes: 170
Popularity: 0.57
First Submitted: 2012-06-13 09:49 (UTC)
Last Updated: 2024-09-29 08:02 (UTC)

Dependencies (13)

Required by (1)

Sources (1)

Pinned Comments

fosskers commented on 2024-07-31 10:21 (UTC)

Aura 4 has been released. If instead you wish you keep using the Haskell-based v3 series, please install:

https://aur.archlinux.org/packages/aura3-bin

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 40 Next › Last »

fosskers commented on 2013-01-14 21:01 (UTC)

To github then, Denis!

dkasak commented on 2013-01-14 14:41 (UTC)

@Colin: Regarding your philosophical issues, I think it's far more important for users to learn what is going on in AUR conceptually, and to get into a habit of checking/researching what they are installing, than to be forced to download a PKGBUILD manually and run "makepkg" (since those are rather trivial things to grasp). So I think the way forward is to think of functionality that will make this conceptual understanding easier and encourage it, rather than sacrificing convenience. Aura is already doing a wonderful job in enabling this with its cool AUR packet introspection features and that's why I don't consider a binary repo a problem. We should probably take the babbling somewhere else if we'd like to continue, though. :-)

fosskers commented on 2013-01-14 01:13 (UTC)

@trusktr: Let me know if that ever comes up again. The key to more users could be a binary repo after all.

trusktr commented on 2013-01-14 01:01 (UTC)

That's odd. I installed it manually. Oh well. What people meant by "binary repo" is for you to create a repo that can be added to pacman.conf. You wouldn't be putting a binary in the AUR. For example, after you create a binary repo, users would have to add something like the following to pacman.conf: [fosskers] Server = http://fosskers.foo/path/to/repo Then to install aura for the first time it'd be as simple as: >> pacman -Sy aura

fosskers commented on 2013-01-14 00:32 (UTC)

I'm not getting that error, trusktr.

trusktr commented on 2013-01-14 00:14 (UTC)

I was trying to install eclipse-android using aura but I get the following error: ┌─[16:11:43/starlancer/trusktr/~] └─╼ sudo aura -Aax --hotedit eclipse-android [sudo] password for root: aura: getCurrentDirectory: does not exist (No such file or directory)

fosskers commented on 2013-01-14 00:01 (UTC)

The reason no third-party package managers / AUR helpers get into the official repos is because the Arch developers maintain that every user needs knowledge of how packages work. They gain this knowledge by building packages themselves with makepkg. I support this view. However, Aura and programs like it are a gateway to _not_ and _never_ do this. Since installing aura means you'll never have to manually build a package again, I was thinking that at the very least I want users to have to build aura themselves. Is this a realistic desire? I realize that the big dependencies are a turn off for some people. The question is, are _most_ people turned off by it? Note that yaourt has a pre-build binary in a user repo somewhere. If we were to put a stable version of aura in a repo and host it somewhere, I'd have one condition. I'd have to be to see download numbers.

dkasak commented on 2013-01-13 23:19 (UTC)

@Colin: I was actually thinking about offering an unofficial pacman *binary repository* (of the kind core, community, extra and similar are) and leaving this package as it is. Adding a hint that the binary repo exists on your upstream github repository might be a good idea (I really wish there was a better way to specify this information on the AUR package page). This is rather common and there are quite a few such repositories: https://wiki.archlinux.org/index.php/Unofficial_User_Repositories. It's easy to set up and has architecture handling built-in (you just compile both versions and name them appropriately), so the only remaining problem is hosting it somewhere, but Dropbox seems to be perfectly fine for that. Your idea of offering an additional binary AUR package (which would presumably just download the binary from somewhere) would also work, but it seems messier.

fosskers commented on 2013-01-13 23:06 (UTC)

@Valantin: aura is updated once a week. Also, gmp is a dependency, not a makedep. @Denis: I was under the impression that binaries weren't allowed at all in the aur, but it seems that's not the case. I suppose I could offer a binary version. However, I think I'd call it `aura-stable-bin` and only update it once and a while. What do you think? Also, how would I deal with different architectures on user machines?

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 40 Next › Last »