[aur-general] Confusing over .AURINFO usage
graysky at archlinux.us
Sat May 4 10:33:54 EDT 2013
On 03/18/2013 08:18 PM, Lukas Fleischer wrote:
>* Changes since 2.0.1:*>**>* * Typeahead suggest for packages.*>* * Fix account editing and hijacking vulnerability.*>* * Fix account privilege escalation vulnerability.*>* * Clear a user's active sessions following account suspension.*>* * Several translation fixes/updates.*>* * pkgsubmit.php: Parse .AURINFO metadata.*>**>* .AURINFO files can now be included in source packages to overwrite*>* specific PKGBUILD fields. .AURINFO files are parsed line by line. The*>* syntax for each line is "key = value", where key is any of the following*>* field names:*>**>* * pkgname*>* * pkgver*>* * pkgdesc*>* * url*>* * license*>* * depend*>**>* Multiple "depend" lines can be specified to add multiple dependencies.*>**>* You can check the Git log  for a complete list of commits.*>**>* The official Arch Linux AUR setup  has already been upgraded!*>**>*  https://projects.archlinux.org/aur.git/log/?id=v2.1.0*>*  https://aur.archlinux.org/*
I created ./.AURINFO which contains a single line:
pkgdesc = NVIDIA drivers for linux-ck.
I ran `makepkg --source` to gen the AUR package but found no traces of
the .AURINFO file therein. Unsurprisingly, the AUR did not pickup on
this when I uploaded the corresponding nvidia-ck-313.30-5.src.tar.gz
package. Are users expected to manually add .AURINFO to the
src.tar.gz post makepkg?
Thanks for the clarification.
More information about the aur-general