| Git Clone URL: | https://aur.archlinux.org/paru.git (read-only, click to copy) |
|---|---|
| Package Base: | paru |
| Description: | Feature packed AUR helper |
| Upstream URL: | https://github.com/morganamilo/paru |
| Keywords: | AUR helper pacman rust wrapper yay |
| Licenses: | GPL-3.0-or-later |
| Submitter: | Morganamilo |
| Maintainer: | Morganamilo |
| Last Packager: | Morganamilo |
| Votes: | 1044 |
| Popularity: | 20.14 |
| First Submitted: | 2020-10-19 00:43 (UTC) |
| Last Updated: | 2024-09-20 18:50 (UTC) |
@MarsSeed As stated in the pinned comment, did you contact her via the github page? I'm not seeing anything from you on there, but I may be missing it.
As you can see from @Popolon's comment, this section seems to mostly be filled with users who do not read the comments before commenting.
But there is a packaging problem that needs to be addressed, as I mentioned in May 2023. It hasn't got any answer yet from maintainer.
@Popolon: FYI, cargo is provided by both rust and rustup. That way, users can use either. cargo-nightly is provided by rustup. That is why the dependencies are the way they are.
@Popolon: No need to change the release version, as it is not out of date.
As Morganamilo said:
Not out of date. Just people flag it as such.
Managed to upgrade it by:
* Changing the release version+sha256sump
* Replacing in makedepends, cargo by rust (now cargo binary is available in rust package)
* Adding openssl in libs dependencies.
@enihcam, you should either ask that on the GitHub, or Google the question, as it pertains to changing the default linker in rust, and is not necessarily paru-specific. Either way, it's not relevant here.
how to link paru objects with mold?
you're better off contacting her via the github, this comments section is 90% "it's out of date" from people who didn't scroll down before posting
+1: From Arch package guidelines (heading 5):
"List all direct library dependencies."
@Morganamilo, please read my polite proposal, and kindly consider declaring openssl or preferably libcrypto.so and libssl.so, which are direct link-level SO-versioned dependencies of paru, in your PKGBUILD.
Otherwise paru can automatically and silently break itself if it removes the legacy version of openssl (like 1.1), even as part of a recursive removal of some other package.
Pinned Comments
haxie commented on 2023-05-26 17:45 (UTC)
you're better off contacting her via the github, this comments section is 90% "it's out of date" from people who didn't scroll down before posting