if your afraid you canât follow the simple instruction, then use yay, pamac or octupi. But just so you know, yay isnât the problem. the problem you ran into was caused by the AUR uploader with his build script and if you donât look at their pkgbuild this can happen.
As a matter of fact, it even states on the AUR WIki the following.
If youâre afraid of yay, then you will have to download and install any software on the AUR from source, usually available on the apps corresponding github page.
Installing manually from source evading the Arch packaging system is not a recommendation I would make lightly. Especially, if the original concern was the risk of system impacting issues. Stray files that both the Arch packaging system and the user are not tracking, are likely to result in future problems.
Fast food is unhealthy.
Therefore food is unhealthy.
Therefore donât eat food.
Or perhaps, we can be discerning about what food we consume, and packages we install from the AUR. The AUR should always be approached with some degree of discernment.
We can take a look at the qdiskinfo-bin PKGBUILD file to see what itâs actually doing:
# Maintainer: begin-theadventure <begin-thecontact.ncncb at dralias dot com>
pkgname=qdiskinfo-bin
pkgver=0.3
pkgrel=1
pkgdesc="Frontend for smartctl providing a user experience similar to CrystalDiskInfo (binary release)"
url="https://github.com/edisionnano/QDiskInfo"
license=('GPL-3.0-or-later')
arch=('x86_64')
depends=('hicolor-icon-theme' 'polkit' 'qt6-base' 'qt6-svg' 'smartmontools')
provides=("qdiskinfo")
conflicts=("qdiskinfo")
source=("$url/releases/download/$pkgver/QDiskInfo-Qt6-libc"
"$url/raw/refs/tags/$pkgver/dist/QDiskInfo.desktop"
"$url/raw/refs/tags/$pkgver/dist/QDiskInfo.svg"
"$url/raw/fc9a25551ad4380d6dce988c0513e85b5fa2fd71/dist/QDiskInfo.png")
sha256sums=('d0172cb70dec29c8b82e7c9317be0c7e2809a4c9e5711095fd34ba0d756c82cd'
'0c5a2436b6777f7871466d85dcc4ce880b597ec112c79991c9cf6a59a428895b'
'f7232af27f88d2ca36c46abebc272976b8e9aa91c7b00c1ae6635c53f09746c6'
'7c237bd42f38cd224b9d2fe2d09c6c1539bc52cd92cecf25a270cf0f52a18a33')
prepare() {
sed -i -E "s|Icon=QDiskInfo|Icon=qdiskinfo|g" QDiskInfo.desktop
sed -i -E "s|Exec=QDiskInfo|Exec=qdiskinfo|g" QDiskInfo.desktop
}
package() {
install -Dm644 QDiskInfo.desktop "$pkgdir/usr/share/applications/qdiskinfo.desktop"
install -Dm644 QDiskInfo.png "$pkgdir/usr/share/icons/hicolor/scalable/apps/qdiskinfo.png"
install -Dm644 QDiskInfo.svg "$pkgdir/usr/share/icons/hicolor/scalable/apps/qdiskinfo.svg"
install -Dm755 QDiskInfo-Qt6-libc "$pkgdir/usr/bin/qdiskinfo"
}
Note the variable url = "https://github.com/edisionnano/QDiskInfo", and thatâs referenced in all the source files:
So we can be certain that this is installing the release version from the official Github page. We can see how it will package this up for installation on your system here:
So for install, itâs bringing in the desktop shortcut and icons, and installing the binary in /usr/bin/qdiskinfo.
You could do all this manually from the same files downloaded from the same place, and evade the Arch packaging system resulting in these files existing un-tracked on your system. Personally, I would just install it using yay.
I agree whole heartedly. But with the this absolute fear of yay he has, this is his only way around using it. Even have to install paru, pamac and octupi you either use the yay command to install from the AUR, or manual install from source.
I wasnât advocating this as the standard way to go, but with his fear from what happened by not reading the pkgbld for his tor-browser experince, this is pretty much the only option he has for this software.
I personally use yay and check pkgbldâs when I do need something from the AUR, which actually only consists of now 5 AUR packages. Heroic, novelWriter, qdiskinfo, Bottles and Windscribe. Everything else I use comes from the standard arch repos.
I know, but I donât know how to do it yet, still learning some things after ~27 years of daily driving linux. Thatâs one of the main things I like about Endeavour, I can learn arch ways of doing things without feeling like my system is fragile because of my own installation errors I could have made.