Package Details: auracle-git r427.33f9097-1

Git Clone URL: https://aur.archlinux.org/auracle-git.git (read-only, click to copy)
Package Base: auracle-git
Description: A flexible client for the AUR
Upstream URL: https://github.com/falconindy/auracle
Keywords: aur
Licenses: MIT
Conflicts: auracle
Provides: auracle
Submitter: Foxboron
Maintainer: artafinde (falconindy)
Last Packager: falconindy
Votes: 123
Popularity: 0.47
First Submitted: 2017-07-02 16:40 (UTC)
Last Updated: 2025-04-16 17:39 (UTC)

Dependencies (13)

Required by (10)

Sources (1)

Pinned Comments

artafinde commented on 2022-01-26 09:15 (UTC) (edited on 2022-01-29 10:24 (UTC) by artafinde)

If the build fails:

  • Clear your aur helper cache and SRCPKGDEST directory
  • Rebuild in clean chroot 1
  • If it still fails, use a paste bin 2 to show full build logs

There's a package build already which you can try out from my repo.

falconindy commented on 2020-05-31 15:35 (UTC)

FAQ:

  • The dependencies are correct. fmt and nlohmann_json are configured as subprojects for ease of development on my end, and it's only natural to statically link C++ projects, as ABI stability with exported C++ libraries isn't a thing (compared to C).
  • If you think pod2man is missing, it's a configuration problem on your end. pod2man is part of the perl package, but in a perl-specific PATH handled by /etc/profile.d/perlbin.sh
  • I'm only able to test auracle on i686 and x86_64, so that's what I'm willing to commit to in the PKGBUILD. If you want to build this on some other architecture, use makepkg -A. The "any" architecture is reserved for packages with architecture independent files (and compiled C++ is not).

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 28 Next › Last »

graysky commented on 2020-04-12 07:46 (UTC)

Setting to 'any' is wrong. It implies compile-specific is not needed. Just build with the -A flag.

lvspais commented on 2020-03-16 21:47 (UTC)

I've built this package on armv7h without any issues just putting the 'armv7h' on the architecture list in PKGBUILD.

I truly think this package architecture could be set to 'any'.

Jarshvor commented on 2020-03-12 23:20 (UTC)

Just to add to TAAPAye's comment I've built it successfully on 'pentium4' architecture by simply listing it in the PKGBUILD.

TAAPAye commented on 2020-02-21 06:59 (UTC)

Is there a reason why only 'x86_64' 'i686' are supported? I built it without problems on aarch64.

user20159 commented on 2020-01-14 17:14 (UTC)

I don't know whether wrapdb is a dependency. But the build failed as there was no fmt available, so therefore I think fmt still is a dependency. And isn't that the main reason why we are using a package manager? That each application doesn't bring it's own dependencys and we end up with multiple copies of the same libraries? And instead having just one copy of that library every application can use? If each project downloads their requirements on it's own, we wouldn't need a centralized package management system. Am I wrong?

falconindy commented on 2020-01-14 17:07 (UTC)

wrapdb is no longer a dependency. I won't dictate whether you install fmt from the repos or via the subproject.

user20159 commented on 2020-01-14 08:29 (UTC) (edited on 2020-01-14 08:30 (UTC) by user20159)

This should depend on fmt, as fmt is a runtime dependency. If makepkg is called without fmt, build will try to use a fallback dependency, which might even fail. As we have fmt in the official repositories, we should use it.

Run-time dependency fmt found: NO (tried pkgconfig and cmake)
Looking for a fallback subproject for the dependency fmt
Downloading fmt source from https://github.com/fmtlib/fmt/archive/6.0.0.tar.gz
Downloading file of unknown size.
Downloading fmt patch from https://wrapdb.mesonbuild.com/v1/projects/fmt/6.0.0/1/get_zip

meson.build:42:0: ERROR: WrapDB connection failed to https://wrapdb.mesonbuild.com/v1/projects/fmt/6.0.0/1/get_zip with error <urlopen error [Errno 113] No route to host>

oats commented on 2020-01-12 19:47 (UTC)

All tests pass on Rpi 4 (armv7h)

falconindy commented on 2019-12-05 18:18 (UTC)

You're expected to have base-devel installed if you want to be building packages. I have no idea why you think pacutils is required.

trougnouf commented on 2019-12-05 17:05 (UTC) (edited on 2019-12-05 17:09 (UTC) by trougnouf)

Requires binutils, gcc, pacutils, pkgconf

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 28 Next › Last »