Install specific version of an AUR package #1068
-
I want to know how to install a specific version and/or branch/commit/tag. I know ArchLinux is a Rolling Distribution and partial Updates are not allowed. That's why i'm using archive.archlinux.org. There are two reasons why I need to specify a specific version (or commit): a) If the AUR packages require a SPECIFIC installed dependency of the regular packages. Example: You stick with
b) avoid re-downloading packages/sources again. The reason is, once a month, I completely rebuild my arch linux from another running linux chroot via a large, well maintained script. This means, I wipe the whole file system except the arch package cache, and the paru cache and some important data directories. I can re-build as often I want, normally, there are no re-downloads. But when paru detects new version, it will force always the latest versions. In case of large binary packages, i there could be several gigabytes of data. FYI: I'm on cell connection only, and mostly I have horrible connection. I have no problems to iterate the commits and check the PKGBUILD version until I find a specifc commit that matches that PKGBUILD file. But even if I have the matching commit, I have no way to tell paru to take that commit. Even if I checkout the commit manually (see my example above), paru will ignore this. Of course, I could take makepkg alone without paru, but then I lose some dependency resolving features, like when an AUR packages requires another AUR package. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
You best bet is to store your pkgbuilds somewhere either via git or on disk then add a pkgbuild repo to paru with
Then you can have your pkgbuild do whatever you want |
Beta Was this translation helpful? Give feedback.
-
I am running into the same issue, especially as Edit: #1084 |
Beta Was this translation helpful? Give feedback.
This won't ever happen because the AUR's API will only give us info on the current version of a package so all dependency resolving and sanity checks go out the window. So it wouldn't really make a sensible feature.
I still think the pkgbuild repo method I suggested is what you want though.