You are not logged in.

#1 2024-08-11 18:34:47

JesseSteele
Member
From: Pacifica
Registered: 2022-07-08
Posts: 11
Website

[SOLVED] How do AUR packages indicate vendor updates? - pkgver()

Rookie question, and no idea where to look.

A PKGBUILD file can use git to create the .pkg.tar.zst locally on the user's machine. So, each time the git repo changes, this same PKGBUILD file (ie from the AUR) will make an updated install, even if PKGBUILD's pkgver= remains the same.

Does the AUR package maintainer need to go in and update PKGBUILD's pkgver= value every single time the git repo is updated?

Or, is there some way for a local `yay -Sy` command to know that an update is available through the AUR's package, but when only the git repo is updated, without the AUR package maintainer editing pkgver= every time?

What is the workflow with this?

Last edited by JesseSteele (2024-08-12 01:59:59)

Offline

#2 2024-08-11 19:03:07

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: [SOLVED] How do AUR packages indicate vendor updates? - pkgver()

JesseSteele wrote:

each time the git repo changes, this same PKGBUILD file (ie from the AUR) will make an updated install, even if PKGBUILD's pkgver= remains the same.

Half true.  Makepkg can be run again on the same PKGBUILD and if it is a properly written -git PKGBUILD, then it will retrieve the latest upstream source, update the pkgver, and build the new package.

JesseSteele wrote:

Does the AUR package maintainer need to go in and update PKGBUILD's pkgver= value every single time the git repo is updated?

No.  Not only do they not need to, they really shouldn't.  If the only change is new upstream commits, the PKGBUILD on the AUR should be left as it is.  But any properly written -git PKGBUILD will have a pkgver function (this also doesn't need to be updated, but it will generate a new version number when it runs again).

JesseSteele wrote:

... is there some way for a local `yay -Sy` command to know that an update is available through the AUR's package, but when only the git repo is updated, without the AUR package maintainer editing pkgver= every time?

Yes - at least with the proper options / flags passed.  Note that `-Sy` are not proper flags for yay as they are passed as it to pacman, and that will result in partial upgrades.  Never use `-Sy` without also including `-u` (i.e., `-Syu` is how you update).

JesseSteele wrote:

What is the workflow with this?

Step 1. remove yay.
Step 2. profit.

Really, it's good to ask these kinds of questions so you can learn, but if you are asking these kinds of questions, you really shouldn't use yay.  As somewhat of a catch-22, exceedingly few people who understand the concepts you ask about would ever think of using yay.  So in the end, really no one should use yay.  Yay delenda est.

Last edited by Trilby (2024-08-11 19:04:03)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2024-08-11 20:12:43

JesseSteele
Member
From: Pacifica
Registered: 2022-07-08
Posts: 11
Website

Re: [SOLVED] How do AUR packages indicate vendor updates? - pkgver()

Trilby wrote:

any properly written -git PKGBUILD will have a pkgver function

...Can you please link or answer me information for how to get that function from:

1. This git repo
2. How it would work for phpMyAdmin

About yay...

Trilby wrote:

Yay delenda est.
Yay must be destroyed. — Google Translate

Step 1. remove yay.
Step 2. profit.


I feel that you aren't being expressive enough about your true feelings concerning yay. Please, feel free to speak your mind and say what you really think.

Last edited by JesseSteele (2024-08-11 20:25:14)

Offline

#4 2024-08-11 20:33:05

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,726

Re: [SOLVED] How do AUR packages indicate vendor updates? - pkgver()

Offline

Board footer

Powered by FluxBB