[aur-general] Confusing over .AURINFO usage

[Lukas Fleischer]

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 at 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.