FS#25521 - Add support for version control in PKGBUILDs

Attached to Project: AUR web interface
Opened by Carlos Jose Ruiz-Henestrosa Ruiz (djoco) - Thursday, 11 August 2011, 21:10 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 19 August 2011, 08:34 GMT
Task Type Support Request
Category PKGBUILD Parser
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 1.8.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Nowadays, it's difficult to install software using version control via PKGBUILDs, specially when using tools like yaourt, because updates don't show up in the AUR. Is there a way to add an option (f.e. "vcs=(array)") to force those PKGBUILDs to be always upgradeable?
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 19 August 2011, 08:34 GMT
Reason for closing:  Won't implement
Comment by Lukas Fleischer (lfleischer) - Saturday, 13 August 2011, 12:01 GMT
Packages are always "upgradable" if you use makepkg(1). This is a problem of $aur_helper failing to deal with VCS packages correctly.
Comment by Carlos Jose Ruiz-Henestrosa Ruiz (djoco) - Sunday, 14 August 2011, 09:10 GMT
I'm talking about adding a variable to make $aur_helper able to manage them without confusing makepkg(1).
Comment by Lukas Fleischer (lfleischer) - Sunday, 14 August 2011, 10:33 GMT
There already are such variables. Keep in mind that makepkg(1) is able to spot VCS packages, so AUR helpers should be able to do that as well. In case you're interested, have a look at makepkg(1)'s devel_check() function.

Loading...