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.58
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 .. 17 18 19 20 21 22 23 24 25 26 27 .. 40 Next › Last »

fosskers commented on 2013-04-04 21:57 (UTC)

Thanks, I'll look into this.

TrialnError commented on 2013-04-04 17:54 (UTC)

Yes, it's pacman 4.1 related. But the changes to the PKGBuild were proposed since 4.0 (Deprecation of PKGBuilds without package() function) So it should work with 4.0 (which is not the case with the new cms PKGBuilds)

fosskers commented on 2013-04-04 00:04 (UTC)

Are you guys using [Testing], and thus have pacman 4.1 already?

TrialnError commented on 2013-04-02 19:40 (UTC)

Not a permission or makepkg issue. in the build function it is not allowed anymore to call $PKGDIR So those install and mkdir commands should move into package() http://pastie.org/7281997

Rasi commented on 2013-04-01 10:22 (UTC)

I cannot build aura. Preprocessing executable 'aura' for aura-1.1.6.0... mkdir: cannot create directory ‘/home/carnager/Downloads/aura/pkg’: Permission denied d--------- 2 carnager users 4096 Apr 1 12:21 pkg changing the permissions manually doesnt help. on next makepkg its changed back again.

fosskers commented on 2013-03-25 09:11 (UTC)

It seems you've put some thought into your request and I thank you for that. How would this be handled manually? Say you were building something big and had all the source you downloaded yourself. The build fails partway through. You try again. Where does that second build start? Does it recognize a good part of the work is already done? (I imagine this depends on the build system) It if does, then I could implement this into Aura. If it doesn't, then I wouldn't even know where to begin. At the moment everything is done in temporary folders. When the build is complete, the .pkg.tar.gz is moved to the cache and everything else is automatically deleted. This could be changed, if the answer to my above question is that it's possible.

trusktr commented on 2013-03-24 22:49 (UTC)

Hi fosskers, I have a feature Request. When a build fails, sometimes the fix is simple, but Aura will start the build over from scratch, which can be annoying if the build takes an hour. Maybe you can give the user the option to try again instead of just quitting, keeping the build files (compiled files) intact for the next attempt so files that have already been compiled won't be compiled again. For example, I had a problem where a build failed due to a missing lib.so file because the file was installed in /opt/package-name/lib instead of /usr/lib/ by it's dependency... To fix the problem, I created a symlink in /usr/lib/ to the file in /opt/package-name/lib/, but it was annoying because compiling the source took a half hour before the error was encountered, so I had to wait a half hour re-compiling only to encounter another missing .so file, so I symlinked it, then started over again, hoping for no more errors... Ideally, instead of quitting, maybe aura can do something like "Build failed. Try again? [y/n]", and that way, before I try again, I can go into another terminal and fix the problem, then try again, and aura won't have to re-compile everything for a whole hour (literally). Aura can keep the build environment intact until the user selects not to continue. Maybe you can create a setting that users can set in a config file for aura (.aurarc?) telling aura not to erase temporary files when it quits, so that if you try installing a package again, it does not have to re-compile the whole thing again. And to make things even better, maybe provide a command line flag to that would tell aura to clear all temporary files. I believe that if the build process pulls new code (e.g. using git), that the make process will only re-compile files that have changed, so this should work. Can you add something like this to Aura?

fosskers commented on 2013-03-24 11:01 (UTC)

1.1.5.0 ------- - `customizepkg` now usable with Aura. Activate with the `--custom` option.

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 40 Next › Last »