A tool to update automatically your PKGBUILDs and push them to AUR

Salamandar · 2015-10-20 18:30:54

Well, when I began to have more than one PKGBUILD to maintain in the AUR I got the idea of this kind of script :

https://github.com/Salamandar/aur-updater

I know it's REALLY not "safe" and pretty, but that's all I had the time to do right now.

I created the (self-updated ) AUR package aur-updater-git if you want to try it.

At first start it creates its own conf file, that you can change at your will :

packages_rootdir="$HOME/tmp/AUR"

packages='fretwork-git fof++-git aur-updater-git'

What do you think about it ?
Hope it can be useful.

Salamandar

Rasi · 2015-10-20 19:31:41

That script does basically... nothing?
It downloads the same version that already was in the PKGBUILD, aka, doesnt check for new versions, doesnt even prompt you to enter a new version number manually.
So all it does is to re-push the exact same PKGBUILD to aur again. for what?

In your example you use git packages. To push changes to a -git package, even though nothing has changed in build system is... useless. git packages will always
build the latest commits anyway.

Last edited by Rasi (2015-10-20 19:33:49)

Salamandar · 2015-10-20 19:33:42

False
When a pkgver function is present inside the PKGBUILD, the makepkg function automatically modifies the PKGBUILD file (the "pkgver=r6.dde4350" line).
I am already using this script, so I am sure it works ^^

And in fact, this script targets the CSV(git, svn, bzr) packages. Those packages have a pkgver function.

Last edited by Salamandar (2015-10-20 19:34:56)

Rasi · 2015-10-20 19:34:52

This is the same as "does nothing".

git packages are always build from master, it doesnt matter which version number you have in your PKGBUILD, because makepkg will update it anyway.
As long as the build system doesn't need changes, -git packages never need an update.

Last edited by Rasi (2015-10-20 19:37:12)

Salamandar · 2015-10-20 19:36:53

Yes, but when a user types "yaourt -Suya", the AUR packages are NOT updated if the maintainer did not update the PKGBUILD with a new version number.

Last edited by Salamandar (2015-10-20 19:37:11)

Rasi · 2015-10-20 19:38:23

wrong.

yaourt --devel

Last edited by Rasi (2015-10-20 19:38:44)

Salamandar · 2015-10-20 19:41:43

Wrong again.
A user does not want to recompile already up-to-date packages. Right now, I don't want to recompile kicad-git (I have the last revision), because it will last 15 minutes.

yaourt --devel

want to recompile kicad-git.

(of course we both mean yaourt -Syua --devel)

Last edited by Salamandar (2015-10-20 19:44:01)

Rasi · 2015-10-20 19:45:27

> yaourt -Syu --devel
...
==> ttf-google-fonts-git is already up to date.

Salamandar · 2015-10-20 19:47:01

Hmmm that's true, I didn't go that far in the compile process. But downloading 300mo to discover that "oh, it's in fact up to date" is not the best solution, is it ?

Last edited by Salamandar (2015-10-20 19:48:33)

Rasi · 2015-10-20 19:50:24

that's probably true. Though I am sure one could tell yaourt not to use /tmp for the git clones.
Anyway. I get the purpose of the tools now.

Last edited by Rasi (2015-10-20 19:50:54)

Salamandar · 2015-10-20 19:55:00

Ok Well basically, it's to "not need" to do this "yaourt --devel". And for a easier up-to-date system for basic users (those who won't do yaourt --devel)

Scimmia · 2015-10-20 20:01:20

Bumping the pkgver of a VCS package when nothing else changes is useless.

Salamandar · 2015-10-20 20:10:21

What do you mean when nothing else changes ? If the pkgver changes, that means that new commits appeared.

Scimmia · 2015-10-20 20:11:34

Which is all handled on the client side. There's no reason to simply bump the pkgver unless you just enjoy annoying your users.

Salamandar · 2015-10-22 18:05:58

Scimmia wrote:

Which is all handled on the client side.

What do you mean ? Read the first comments before repeating the same thing…

Scimmia · 2015-10-22 20:39:51

Salamandar wrote:

Scimmia wrote:
Which is all handled on the client side.
What do you mean ? Read the first comments before repeating the same thing…

I mean that everything is updated when the person building it runs makepkg. Pushing an updated PKGBUILD to the AUR every time there is new commits upstream is just silly.

Arch Linux

#1 2015-10-20 18:30:54

A tool to update automatically your PKGBUILDs and push them to AUR

#2 2015-10-20 19:31:41

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#3 2015-10-20 19:33:42

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#4 2015-10-20 19:34:52

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#5 2015-10-20 19:36:53

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#6 2015-10-20 19:38:23

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#7 2015-10-20 19:41:43

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#8 2015-10-20 19:45:27

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#9 2015-10-20 19:47:01

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#10 2015-10-20 19:50:24

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#11 2015-10-20 19:55:00

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#12 2015-10-20 20:01:20

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#13 2015-10-20 20:10:21

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#14 2015-10-20 20:11:34

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#15 2015-10-22 18:05:58

Re: A tool to update automatically your PKGBUILDs and push them to AUR

#16 2015-10-22 20:39:51

Re: A tool to update automatically your PKGBUILDs and push them to AUR

Board footer