Search Criteria
Package Details: rua 0.19.10-2
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: | 59 |
| Popularity: | 0.39 |
| First Submitted: | 2018-10-29 14:26 (UTC) |
| Last Updated: | 2025-02-13 14:43 (UTC) |
Dependencies (10)
- bubblewrap (bubblewrap-gitAUR, bubblewrap-suid)
- git (git-gitAUR, git-glAUR)
- pacman (pacman-gitAUR)
- xz (xz-gitAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- libseccomp (libseccomp-gitAUR) (make)
- sed (busybox-coreutilsAUR, sed-gitAUR) (make)
- bubblewrap-suid (optional) – version of bubblewrap that works on linux-hardened kernel
- shellcheck (shellcheck-binAUR, shellcheck-gitAUR) (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, fudo-gitAUR, sudo-selinuxAUR) (optional) – allows package installation via sudo, if desired
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »
vasya commented on 2019-10-25 08:21 (UTC) (edited on 2019-11-04 16:33 (UTC) by vasya)
Those who upgraded pacman in the last days will notice that RUA becomes broken. This is caused by a change in pacman-s underlying library, "libalpm".
You need to install RUA version 0.14.16 or newer to make it work with newest pacman. You can use
makepkg -siorcargo install --force ruato re-build RUA, as per instructions here: https://github.com/vn971/rua#install-dependenciesvasya commented on 2018-10-31 00:11 (UTC)
I've removed all
rustupinvocations from the PKGBUILD. Something worth considering though is that ~/.cargo (and possibly ~/.rustup) are shared with normal $HOME anyway. I guess that's a common property of all AUR packages using cargo though.vasya commented on 2018-10-30 23:23 (UTC)
@eschwartz, to address a very specific comment:
Said problem appears whenever rustup is used. If you haven't used it before (for this unix user), this is what you'll get.
Regarding $HOME. Would using
cargoitself be safe? It does fetch dependencies and store them in ~/.cargo too... I'd really want a way around this myself...vasya commented on 2018-10-30 23:17 (UTC) (edited on 2018-10-30 23:17 (UTC) by vasya)
@Morganamilo > Why not just depend on rust? -- That would be ideal. Unfortunately, however, the "rustup" and "rust" packages are in conflict. If the user already uses "rustup", they will have to uninstall it.
coderobe commented on 2018-10-30 23:17 (UTC)
Eli already echoed what i told you on IRC earlier, but for some reason you've only removed parts of it. Could you please get rid of the rest as well? Your package is not special, and this dance is not required - not to mention that your implementation of said hack isn't particularly good either. Seeing your complete lack of understanding on irc regarding this, consider this a warning...
eschwartz commented on 2018-10-30 23:11 (UTC)
puts on Trusted User hat
Suddenly using rustup and installing a toolchain to the user's $HOME is not okay, moreso when the need for doing so is only if you're using your own unsupported helper which breaks this.
If users use rustup, that's their problem, and I guess they shouldn't use toolchains that install themselves to
$HOMEin order to build packages. This very program was supposedly supposed to prevent issues like this -- it's ironic that the only way to build this PKGBUILD in a sane manner, is to use the program you haven't built yet to do it!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?
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »