Search Criteria
Package Details: rua 0.19.10-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/rua.git (read-only, click to copy) |
|---|---|
| Package Base: | rua |
| Description: | AUR helper in Rust providing control, review, patch application and safe build options |
| Upstream URL: | https://github.com/vn971/rua |
| Keywords: | aur rust |
| Licenses: | GPL3 |
| Submitter: | vasya |
| Maintainer: | vasya |
| Last Packager: | vasya |
| Votes: | 57 |
| Popularity: | 1.11 |
| First Submitted: | 2018-10-29 14:26 (UTC) |
| Last Updated: | 2024-01-02 23:51 (UTC) |
Dependencies (9)
- bubblewrap (bubblewrap-gitAUR, bubblewrap-overlayfsAUR, bubblewrap-suid)
- git (git-gitAUR)
- pacman (pacman-pbAUR, pacman-fancy-progress-gitAUR, pacman-gitAUR)
- xz (xz-gitAUR)
- cargo (rust-nightly-binAUR, cargo-gitAUR, rustup-gitAUR, rust, rustup) (make)
- libseccomp (libseccomp-gitAUR) (make)
- bubblewrap-suid (optional) – version of bubblewrap that works on linux-hardened kernel
- shellcheck (shellcheck-gitAUR, shellcheck-binAUR, shellcheck-bin-docAUR) (optional) – allows checking PKGBUILD scripts, taking care of special variables
- sudo (fake-sudoAUR, polkit-fakesudoAUR, sudo-gitAUR, doas-sudo-shimAUR, doas-sudo-shim-minimalAUR, sudo-hgAUR, sudo-selinuxAUR, fudo-gitAUR) (optional) – allows package installation via sudo, if desired
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7
vasya commented on 2018-10-30 19:18 (UTC)
Morganamilo: I guess it's kinda controversal then. From my point of view, requiring anything at all from $HOME when building packages is not nice. Had this story with some PKGBUILDs before, was never happy when such constraint breaks. Especially because I build packages from a separate user. Let's leave it as-is then, for now.
Morganamilo commented on 2018-10-30 18:54 (UTC)
I'll say that AUR helpers are not supported.
If this package fails to build because of a specific helper then it should be on the helper to make it work, not the pkgbuild. (even if this pkgbuild is for that helper).
But that's just what I think. If you do care about having a good pkgbuild you should probably ask on the forums/mailing list/irc to see what they come up with.
vasya commented on 2018-10-30 18:10 (UTC) (edited on 2018-10-30 18:11 (UTC) by vasya)
Morganamilo: another thing about rustup and RUA. The latter currently isolates your $HOME directory, unless you whitelist some paths in ~/.config/rua/wrap_args.sh. So if you e.g. build RUA inside stock RUA, the PKGBUILD script will have empty $HOME and will not be able to work without a rustup command. I understand that it soulds like unneeded complexity, but naturally, I do want this PKGBUILD to be buildable in a clean environment.
Put it another way. If the environment is shared and properly configured, then these configuration lines will never be "hit". Thoughts?
Morganamilo commented on 2018-10-30 16:39 (UTC)
If a user decides to use rustup it should be their responsibility to manage it. I think it's a bad idea for a pkgbuild to start installing something.
To rephrase what I said. Why not just depend on there already being a valid rust environment already set up like other packages do?
vasya commented on 2018-10-30 16:19 (UTC) (edited on 2018-10-30 16:21 (UTC) by vasya)
Morganamilo: the package does in fact depend on
cargo, which is provided by bothrustandrustup. So if you haverustinstalled, everything will work just fine for you.If, however, you decide to go with
rustup, you NEED to also download&install the stable version usingrustupitself. This is a rustup limitation, not mine.EDIT: in other words, users that decide to use
rustupcannot just install it via pacman and be ready to build.:( The missing steps are ensured by this PKGBUILD.Morganamilo commented on 2018-10-30 15:41 (UTC)
Whats up with the rustup calls? Why not just depend on rust? I don't see any reason a pkgbuild should trigger an update/install of something. Especially something not managed by pacman.
« First ‹ Previous 1 2 3 4 5 6 7