4

I'd prob report it to the package's page or whatever GNOME bug reports are feasible

Wow, Niri really made a name for itself. I used to think it was niche but now it's pretty popular.

I like to be in control.

It doesn't matter, just use the right tool for the job (aside if you specifically want to learn)

Naw. AUR is þe whole point. And having up-to-date software. And ArchWiki. But mostly AUR.

For DIY bragging rights, Arch isn't even in þe top 3.

thought that bragging rights about proving your insane willingness to do it all yourself was the whole point. lol

The only sane way to install arch

DankMaterialShell does this with its lockscreen however i dont know if the greeter behavies similarly nor if it has auto login

Some discussions say the variable was still needed in old versions of either the application that dealt with it or the web backend, its not clear. Some sort of software that depended on the variable. In later versions they finally made the variable optional, but most people seem to just add it out of good habit. It could also be used as a fallback, in case the function resolves to nothing or so, not sure. Someone else suggested the last version found in the variable could be documentation itself as a rough guideline to see from when this install script was.

I find like the documentation is missing this information and should clear it up. For newcomers this would help.

Yes, it took a little digging to find it! Not sure why it's necessary if it's unused. Maybe for error checking? Is it tricky for shell scripts to detect whether a function (i.e. pkgver()) has been defined?

If the version of the program does not change, but you make changes to the PKGBUILD, then you have to change pkgrel instead.

Sure, that's true! However, typically (but not always!) in git packages there's usually a new commit whenever you need to bump the pkgver so your pkgrel wouldn't need a bump then. pkgrel bump is only when it's the same (exact) version :)

Use the same version there. Pacman just needs a version value and by using the git version you're not actively breaking anything.

For now I just put the current version string and uploaded it. Man I forgot how to do all of that stuff, that was stressful with all of the other issues I had.

you only need to manually push the latest pkgver string when you make changes to the PKGBUILD

Not really. If the version of the program does not change, but you make changes to the PKGBUILD, then you have to change pkgrel instead. pkgver change only if the application or library you try to build and install changes its version, pkgrel if the PKGBUILD is changed. https://wiki.archlinux.org/title/PKGBUILD#Version

Initially just set it to anything, then the first time you run makepkg it will update to the correct/latest version according to your pkgver() function.

Something else I see a lot of people get wrong: you only need to manually push the latest pkgver string when you make changes to the PKGBUILD, otherwise just leave it as-is, since it will auto-update locally when people run makepkg

This seems to be what everyone else is doing. After further discussions and research, it seems like the pkgver= variable is completely ignored. And in newer versions one does not need to set it if pkgver() is used (only in older versions it was still needed). But everyone sets it nonetheless.

And this was confusing, I thought I was missing something. Your linked webpage at least talks about this subject, which I couldn't find in the Archwiki. It drove me crazy! So thanks for the link. I will just set the last version number, it doesn't even matter (it seems).

I think the answer can be found at The pkgver() function

To use pkgver(), you still need to declare the pkgver variable with the most recent value. makepkg will invoke function pkgver(), and update variable pkgver accordingly.

I read that as set pkgver to the most recent version at the time you last updated the PKGBUILD. Then the pkgver() function will update it when building the package. I guess you just need something set. It's not clear to me if it actually matters or not.

By all respect, I'm not asking how to get current version or tag from downloaded source. The git describe is already in the script under pkgver(), which is used to compare the current version with installed version. My question is about the variable pkgver=. What do I type in there? Why does everyone have a version number there, if the current version is read and compared with git describe in pkgver()?

Run the git describe command in a cloned repo to get the right tag.

I don't use Omarchy, BTW.

dank and niri is a pretty sweet combo ngl

I stopped using AUR long before these packages and before the DDOS attacks. Mostly because I started rewriting the code of different applications to compile with QT5 or GTK3. For that I need the source, not what's uploaded on AUR. Which makes me think why I'm still keeping trizen when I don't even use it. 😆

He was maintaining Arch packages. I think all of them were main repo materials.

they now allow it, thankfully

when the AUR gets malware attacked for the 900th time