Arch Linux

arsenist

Member

Registered: 2008-07-06

Posts: 30

Yaourt upgrade issue with repos

Hi !

When I upgrade a package that's in developpement (git/hg/svn repos) with yaourt.
Example for the awesome-git package:

$> yaourt -Ss awesome-git
aur/awesome-git 20080919-1 [20080926-1 installed]

$> yaourt -S awesome-git
....
bla bla bla everything goes fine
....

$> yaourt -Ss awesome-git
aur/awesome-git 20080919-1 [20080926-1 installed]

My question is, why does it say i've got a different version installed ? oO

Thanks !

Profjim

Member

From: NYC

Registered: 2008-03-24

Posts: 658

Re: Yaourt upgrade issue with repos

Let's see if I understand this right.

Most PKGBUILDs are static. If they say version 213, and you run makepkg on them, they'll keep saying version 213.

Version-Control based PKGBUILDs are smarter. If they say version OldDate, and you run makepkg on them, and the data in the remote version control server is newer than you've got downloaded, then they'll go fetch the changes from the server, and *update the PKGBUILD to reflect the update.* Now the PKGBUILD will say NewDate. (I'm not quite sure if NewDate is the date that makepkg is being executed, or the date of the latest change stored on the version control server. I think it's the latter.) So every time you run makepkg on this PKGBUILD, it may end up changing the PKGBUILD. But no one is reloading the PKGBUILD to AUR every time this happens. AUR will just have the PKGBUILD with the version # that was current when the PKGBUILD was saved on AUR.

In short: you should EXPECT your svn/git/hg/and so on PKGBUILDs to have newer version #s than it says on aur.

arsenist

Member

Registered: 2008-07-06

Posts: 30

Re: Yaourt upgrade issue with repos

That makes sense !
Thanks a lot for taking the time .