On 08/28/2010 10:32 PM, Nicky726 wrote:
Hello,
hope I don't get this missplaced, as a quick search didn'd get me any results.
When I have a package, which does actually build nothing -- say wine_gecko (a file only needs to be placed to a correct directory) -- I should only have package() function in the PKGBUILD, is that a correct interpretation?
Now the makepkg is happy but the AUR complaints. I can workaround that with an empty build() function in that case the AUR is happy but the makepkg complains. So I just put in there a harmless echo and both are happy now. Actually my question is not that much about the correct workarounding, as it is about if I really get the meaning of the build() and package() functions correctly, that is for building build(), for installing package()?
Thanx, Nicky.
Hi Nicky, your interpretation sounds very sensible to me. The related AUR-bugreport is here: http://bugs.archlinux.org/task/19914 The bug is fixed in the git-repository, but the software on aur.archlinux.org was not updated after that patch was applied. An update of the AUR is not scheduled yet. Regards, PyroPeter -- freenode/pyropeter "12:50 - Ich drücke Return."