Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use .SRCINFO instead of PKGBUILD for pkgbase e.a. querying #135

Open
AladW opened this issue Mar 19, 2018 · 2 comments
Open

Use .SRCINFO instead of PKGBUILD for pkgbase e.a. querying #135

AladW opened this issue Mar 19, 2018 · 2 comments

Comments

@AladW
Copy link

AladW commented Mar 19, 2018

SRCINFO has a more stable format than PKGBUILD as it is a simple key/value format generated by the user. It contains the same metadata the PKGBUILD contains. (*) For example, compare:

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=aws-cli-git

to

https://aur.archlinux.org/cgit/aur.git/tree/.SRCINFO?h=aws-cli-git

(*) The SRCINFO has to be explicitely generated by the maintainer, but this shouldn't be a problem since the AUR warns explicitely on this when pushing changes.

@f2404
Copy link
Collaborator

f2404 commented Apr 1, 2018

Thanks for the suggestion, you're welcome to provide a patch ;)

Please make sure to leave the existing code for PKGBUILD and fall back to it in case of missing .SRCINFO file or if it doesn't have the field we're looking for.

@ghost
Copy link

ghost commented Nov 6, 2018

PKGBUILD downloading and parsing is only done to get single arch field (#121, #122) and is discarded right away, see aur.c#L798.

I think this is out-of-scope of what package-query should do and to be provided by tool that handles AUR packages not just queries RPCs e.g. by yaourt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants