On Sat, May 4, 2013 at 10:54 AM, Lukas Fleischer <[email protected]>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?
