On 18/03/13 19:18, Lukas Fleischer wrote:
Changes since 2.0.1:
* 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.
I've read a couple of threads [1][2] relating to this topic, and I am
puzzled by the idea of using .AURINFO files to "overwrite" PKGBUILD
fields. What is the use case for this? It seems completely different to
the idea behind .SRCINFO files. Have there been some other discussions
on this topic that I've missed?
[1]
https://mailman.archlinux.org/pipermail/pacman-dev/2012-August/015900.html
[2] https://mailman.archlinux.org/pipermail/aur-dev/2013-March/002392.html
