You are not logged in.
# Contributor: Michel Brabants <michel.linux@tiscali.be>
pkgname=mlt++-cvs
pkgver="$(date +"%Y%m%d")"
pkgrel=2
pkgdesc="MLT C++ binding"
#ffmpeg from cvs?
#libsamplerate>=0.1.2 ok? The documentation says that the version should be greater than 0.15. Could be not ok.
depends=('mlt')
makedepends=('coreutils' 'cvs' 'patch')
source=('Makefile.patch')
md5sums=('c8af785af43374491aac12ab37286442')
cvsuser="anonymous"
cvspassword=""
cvsrepositorylocation="cvs.sourceforge.net:/cvsroot/mlt"
cvsdirectory="mlt++"
build() {
#download source from cvs-repository
#if mlt wasn't downloaded today, download it then. Give the downloaded directory a more unique name
if [[ ! -x $startdir/src/$pkgname-$pkgver ]]; then
cd $startdir/src
cvs -d:pserver:$cvsuser:$cvspassword@$cvsrepositorylocation login
cvs -z3 -d:pserver:$cvsuser:$cvspassword@$cvsrepositorylocation co $cvsdirectory || return 1
mv "$cvsdirectory" "$pkgname-$pkgver"
#else update it in existing directory
else
cd "$startdir/src/$pkgname-$pkgver"
cvs update -dP
fi
cd "$startdir/src/$pkgname-$pkgver"
#patch Makefile so it doens't run ldconfig
patch src/Makefile ../Makefile.patch
./configure
make || return 1
mkdir -p $startdir/pkg/usr/lib
make prefix=$startdir/pkg/usr install
}
--- Makefile 2004-12-24 11:09:14.000000000 +0100
+++ Makefile-new 2005-08-14 15:48:55.000000000 +0200
@@ -44,5 +44,5 @@
$(INSTALL) -m 755 $(TARGET) $(prefix)/lib
$(INSTALL) -d "$(prefix)/include/mlt++"
$(INSTALL) -m 644 $(HEADERS) "$(prefix)/include/mlt++"
- /sbin/ldconfig || true
+# /sbin/ldconfig || true
Offline
...snipp #ffmpeg from cvs? ...snap
ffmpeg in testing actually is a snapshot. Even the developers of recommend using it, so I wonder why they don't release stuff. An alpha-bata-rc-whatever
tarball would even be nice.
But for you the testing package should be sifficient.
-neri
Offline
Heya,
same comments as for the mlt-package:
I made it a little bit more conform to archlinux packaging standards. It hopefully won't ask for a password anymore. I also changed the name of the package to "mlt-cvs". I also changed the date, so it makes a new package for each day and not for each hour.
It is not completely conform to the standard/example, but I'll notice if they like it. I've seen there is a script to automate the building of cvs-buildfiles. It may not work with my buildfile. I probably will remove the date-command. However, I like the flexibility of my cvs-variables ... I'll have to see how it compares to the archlinux-packaging standard and what comments I get about it from others.
greetings,
Michel
Offline
Heya,
I will probably upload this package to the AUR, but was wondering what people thought about the way I habdle cvs. It is a different than in the standard guidelines. I was wondering if I have to change it if I upload it to the AUR?
greetings,
Michel
Offline
You could put an underscore in front of your "home-made" variables to conform to the guidlines about that. For the pkgver, you might want to changed it to a fixed number otherwise the AUR will garble it (see the amsn-cvs package).
Offline