AUR web interface

**This is the bug tracker for the AUR web interface.**

Use this tracker to report bugs or make feature requests regarding the behaviour or implementation of the AUR software.
Please read the Reporting Bug Guidelines before filing a new task.

- Please report bugs related to Arch Linux official packages here:
- Please report bugs for [community] packages here:
- For any packages in the AUR contact the maintainer or leave a comment on the package's detail page.

Source Code:

FS#27254 - Add cross references between "package" and "package-vcs"

Attached to Project: AUR web interface
Opened by Julien Nicoulaud (nicoulaj) - Friday, 25 November 2011, 17:53 GMT
Last edited by Lukas Fleischer (lfleischer) - Sunday, 18 November 2012, 00:09 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Very Low
Priority Normal
Reported Version 1.9.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


It would be nice the page of a package contained a link to the page of the VCS version of the package if it exists, and reciprocally.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Sunday, 18 November 2012, 00:09 GMT
Reason for closing:  Won't implement
Comment by Lukas Fleischer (lfleischer) - Friday, 13 April 2012, 09:29 GMT
How do we spot VCS versions? Use a set of common suffixes (such as "-git", "-hg", "-svn")? What about false positives such as bzr-svn? What do we do if the (non-)VCS version is in any of the official repos?
Comment by Julien Nicoulaud (nicoulaj) - Friday, 13 April 2012, 11:33 GMT
> How do we spot VCS versions? Use a set of common suffixes (such as "-git", "-hg", "-svn")?
I guess using a set of common suffixes + PKGBUILD makedepends containing the suffix should eliminate all false positives ?