As it turns out you don't have a stable release tarball in the Files
area but if you did then if the item in the sources=() array was a
full http:// URL, pointing to the release tarball, then a regular
Archlinux "makepkg" invocation would auto download it and build a
binary package. As it stands now it would be expected that a tarball,
generated locally from a svn checkout, would need to be in the local
source cache area. This would set it up with a locallay cached
tarball...

build() {
  cd $SRCDEST
  if [ -d $SRCDEST/$pkgname/.svn ]; then
    cd $SRCDEST/$pkgname && svn up
  else
    svn checkout svn://svn.berlios.de/$pkgname/trunk $pkgname
  fi
  mv $pkgname $pkgname-$pkgver
  tar cjf $pkgname-$pkgver.tar.bz2 $pkgname-$pkgver --exclude-vcs
  mv $pkgname-$pkgver $pkgname
  cd $srcdir/$pkgname-$pkgver
  ./configure --prefix=/usr
  make AUTODEP=0 all || return 1
  make INSTALL_PREFIX=$pkgdir install || return 1
}

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Lensfun-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lensfun-users

Reply via email to