AUR web frontend sources URL problem

Question

Sometimes the $pkgname is different from source package tarball filename, so it is necessary to use a different variables.. For an imaginary foo package, with sources available at http://foo.org/foo-linux-1.2.tar.gz , the PKGBUILD fragment may look like
pkgname=foo
pkgname0=foo-linux
pkgver=1.2
source=('http://foo.org/$pkgname0-$pkgver.tar.gz')
unfortunaly, in such case, the AUR web page points to a wrong sources URL: http://foo.org/foo0-1.2.tar.gz . It looks like the frontend thinks that the source URL must contain $pkgname, and is doing simple string substitution, not interpreting the PKGBUILD as a shell script.
Is there already a working way how to form the PKGBUILD, to avoid this sort of problem ?
Last edited by mykhal (2007-09-02 17:28:50)

Answer 1

tardo wrote:...I don't think I'll ever flag the openssh pkg as safe because you're implementing completely new functions not found in the official package. Other than that, fix the others and you're good to go =/
thanks for the review.
If you look more carefully at the openssh patch, it is not implementing anything new, openssh has an infrastructure for using hardware engines (engines.h), but is not used by default somehow, the patch is just enabling it. Anyway, I'm not creator of the patch, is it taken from Michal Ludvig's site (http://www.logix.cz/michal/devel/padlock/) , some of his patches have also been accepted in linux kernel.
But I understand, this is very sensitive package..