[SOLVED] .AURINFO and makepkg --source

Question

The documentation suggests that one use
makepkg --source
to build source packages for AUR, but also states that one should include a .AURINFO file.
See Arch User Repository and Arch Packaging Standards
I made a .AURINFO file by hand and placed it in the same directory as PKGBUILD, but the problem is that makepkg --source doesn't pick it up and include it in the src .tgz file.
It doesn't seem like makepkg --source is doing much more than putting PKGBUILD in a compressed tarball.  I can create such a tarball by hand myself, but am wondering if I'm missing something?  In any case, the documentation appears to be inconsistent.
AUR Metadata suggests using mkaurball as a wrapper for makepkg --source.  That seems like overkill for the package I'm trying to put in AUR.  I'd rather keep it simple (in accord with the Arch philosophy) whenever possible.
Last edited by pgoetz (2014-04-03 16:14:06)

Answer 1

progandy wrote:
You could add the file in a custom script with something like this:
bsdtar -cf example-1.2.3-1.aur.src.tar.gz example/.AURINFO @example-1.2.3-1.src.tar.gz
This is probably worth documenting in the AUR and AUR Metadata Wiki pages -- I'll do that now.
EDIT:  So, there are some problems with this approach that were discussed outside the forum.  You can make this work (i.e. using bsdtar to add .AURINFO to the source tarball), but you have to be very careful about the file locations when you're executing something like the command above, else the .AURINFO file won't untar into the same directory as the PKGBUILD file.
See the AUR Metadata Wiki page for details on how get .AURINFO into your source package.
Last edited by pgoetz (2014-04-05 08:43:12)