Cvs daily snapshot packages

Question

Hi there,
I have some questions about cvs daily snapshot.
The problem is for the package eo-snapshot in AUR
Here is the PKGBUILD
# Contributor: Sebastien Piccand <[email protected]>
pkgname=eo-snapshot
pkgver=20060411
_ver=11Apr2006
pkgrel=1
pkgdesc="EO is a templates-based, ANSI-C++ compliant evolutionary computation library"
url="http://eodev.sourceforge.net/"
license="LGPL"
depends=()
source=(http://www.lri.fr/~marc/EO/snapshot/eo_src.tgz)
md5sums=('f4e001d00405292712e5a62599749c3d')
build() {
cd $startdir/src/eo${_ver}
./autogen.sh
./configure --prefix=/usr
make || return 1
make DESTDIR=$startdir/pkg install
I have to remove the _ver variable which is not required.
I have to use the daily snapshot because:
1. The stable version does not compile
2. I don't have access to CVS
The version(=folderOfSources=date) of the package is a bit weird and stored as:
11Apr2006.
I was asked to change the version so I moved it to 20060411 which seems to be the case for the usual snapshots.
I used the variable _ver so that one has just have to modify the beginning of the PKGBUILD when a new snapshot comes. But it is definitely not really needed so I have to remove it, which means you have to edit the build() function at each snapshot.
A workaround is to use
cd $startdir/src/eo*
instead of
cd $startdir/src/eo11Apr2006
in the build(function)
In this case now the version of the snapshot is only discriminated by:
1. the pkgver
2. the md5sum
But the package is updated daily and there should be a way to simplify the  update process. The daily snapshot does not contain the date so we can't have access to the previous snapshot.
Can I, as for the CVS versions, use an empty md5sum() and just the date for the pkgver ?
Or should the package be a mess to maintain ?
Thanks

Answer 1

Thanks a lot.
The package is working.
I now have some questions about the provides() and conflicts() fields of some packages.
Here are 2 packages I put on AUR recently: eo-snapshot, eo-cvs
I am thinking of removing eo-snapshot but it can be good to keep it for people who don't have access to CVS.
In this case eo-snapshot and eo-cvs will conflict. Once a new, working, stable version of eo will be out, I (or anybody) will probably make a package (called eo).
So I am thinking of using the fields provides=('eo') for both packages, and conflicts=('eo-snapshot') or ('eo-cvs')
Is it the right thing to do ?
An other question:
libge can use galib if it is compiled with galib support, so should I make a libge-galib version (with galib in makedepends) or put a comment somewhere (where) that asks the user to install galib before building libge to enable the galib support ?
An other one
eo-cvs(or eo-snapshot) and galib both provide a /usr/lib/libga.a file, so they conflict with one another. Is there any workaround to install both?