[aur-general] Confusing over .AURINFO usage

[Christoph Vigano]

On 04.05.2013 17:29, 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
> 

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

Greetings,
Christoph

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20130504/5d45b634/attachment-0001.asc>