Suggestion of Packages for the EndeavourOS Repo

You can use a pkgver function. Just look at one of these other *-git PKGBUILDs

I already did. And for me it seems they update the PKGBUILD manually everytime? Or runs a cronjob or something on the AUR Server wich updates this automatic?

Nope, that would be to crazy ;). The “magic” is in the pkgver function in the PKGBUILD file which is dynamically creating the version number during build. Now AUR helpers like yay, for example store the last commit hash when you build the package and check that against the lasted commit hash in the remote git repository (if you enabled that in yay…)

See: https://wiki.archlinux.org/title/VCS_package_guidelines for details.

edit ah, too late, @dalto beat me :wink:

Is this automatic enabled? Because i didnt changed anything in yay, and it updates any -git package i have installed.

You either do yay -Syu --devel to check for repo package + AUR packages + AUR -git packages

or what you can do as well is to enable the --devel (-git check) flag permanently with:

yay -Y --devel --save

That way, you just need to run yay and it’ll basic upgrade anything (like yay -Syu --devel does).

1 Like

Yeah ok. But i never do that this way.

I simply do yay -Syu. And didnt changed any configuration from yay.

And it updates packages if new commits are available (for a USB WLAN dongle for example on a other system from me). So they maintainer must it do it a another way?

Save yourself 4 keystrokes…all you need to type is yay.

1 Like

hehe. I only wrote i do that. In reality i do yay -Syyu. But i dont wanted to trigger somebody :rofl:

1 Like

Well, yeah for “normal” (non -git) packages the maintainer has to update the version manually.

For -git it works this way:

  1. Check pkgver in .SRCINFO (in AUR) against the locally installed version → If newer → Rebuild/Upgrade package (this is how it works with normal packages as well)
  2. If the versions are the same, the commit hash check is performed as mentioned above.
1 Like

You won’t trigger anyone but they will probably tell you it is totally unnecessary unless you changed mirrors or added a repo or something.

1 Like

ok, so the maintainer from this package https://aur.archlinux.org/packages/rtl8821au-dkms-git/

updates the PKGBUILD manually. Because this package gets on my mentioned System reguarly updated, without any flags or options on my side.

Yeah. Im simply paranoid… Its a left over from gentoo times.

Yes, some maintainers might do that to make sure the people using his/her -git package are getting updates even when they do not use the e.g. “–devel” feature in yay. (I sometimes use to do this as well if I think “it’s worth it”). A lot of people know don’t about the --devel / VCS check thing so…

Generally -git packages though are not being updated by the maintainer unless there are other changes to the PKGBUILD file other than the version…

He triggers me. I’m operating a couple of mirrors and I don’t want bandwidth to get wasted :rofl:

2 Likes

It’s purposely wasting your money every time they do that. I’d be pissed.

1 Like

It’s a couple of VPS’s / root servers with a fixed price / month. Luckily traffic does not really matter (there is a certain threshold when bandwidth is being throttled, but I’m still far away from that fortunately).

But yeah, if one doesn’t know better, or if in doubt, ok…
If it’s really on purpose (like: “I want to generate useless traffic”) → FU :wink:

2 Likes

Im sorry :kissing_heart:

:astonished:

1 Like

As i worked today again after all the holidays, i just wanted to report that the import over cli worked flawlessy!

Thanks for the tip.