On Sat, May 04, 2013 at 11:01:55AM -0400, member graysky wrote:

On Sat, May 4, 2013 at 10:54 AM, Lukas Fleischer <archlinux@cryptocrack.de>wrote:

...

...

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?

As you can guess from the name, .AURINFO is AUR specific. Thus it is not added by makepkg(8). You can add it manually -- make sure you put it into the subdirectory, though.

Of course, we aim at creating meta data automatically at some point, so feel free to come up with something that parses source packages, generates .AURINFO and adds them to the tarball.

Thanks, I get it. This definitely seems like something makepkg should detect and handle automatically Are the .AURINFO files here to stay?

Note that .AURINFO functionality will not be added to pacman/makepkg, unless the format is extended to work with split packages and all corner cases that we do not care about in the AUR. The idea is to start with an external tool to post process source packages and then extend this tool, as well as the underlying .AURINFO format, until we get something that is suitable for integration with makepkg.

On 04.05.2013 17:29, member graysky wrote:

On Sat, May 4, 2013 at 11:18 AM, Lukas Fleischer <archlinux@cryptocrack.de>wrote:

...

...

Thanks, I get it. This definitely seems like something makepkg should detect and handle automatically Are the .AURINFO files here to stay?

Note that .AURINFO functionality will not be added to pacman/makepkg, unless the format is extended to work with split packages and all corner cases that we do not care about in the AUR.

The idea is to start with an external tool to post process source packages and then extend this tool, as well as the underlying .AURINFO format, until we get something that is suitable for integration with makepkg.

OK. I haven't tested this with split packages, but the attached patch works with a non-split one for those too lazy to manually make the modified src.tar.gz :p

Another solution mentioned by someone else here on the list seems to be to include the .AURINFO in the source array. Greetings, Christoph

On Sat, May 04, 2013 at 11:29:07AM -0400, member graysky wrote:

On Sat, May 4, 2013 at 11:18 AM, Lukas Fleischer <archlinux@cryptocrack.de>wrote:

...

...

Thanks, I get it. This definitely seems like something makepkg should detect and handle automatically Are the .AURINFO files here to stay?

Note that .AURINFO functionality will not be added to pacman/makepkg, unless the format is extended to work with split packages and all corner cases that we do not care about in the AUR.

The idea is to start with an external tool to post process source packages and then extend this tool, as well as the underlying .AURINFO format, until we get something that is suitable for integration with makepkg.

OK. I haven't tested this with split packages, but the attached patch works with a non-split one for those too lazy to manually make the modified src.tar.gz :p

Not sure if you got me wrong but I was talking about a tool that *generates* .AURINFO files (e.g. by sourcing PKGBUILDs and printing the values of variables), not about a tool that just automates the inclusion of a handcrafted file. Also, while I disagree that using the sources array is the right place to add this kind of metadata, I agree that this should not be implemented in makepkg(8) until it is extended, renamed, reviewed and acknowledged by the pacman development team.