[Kolab-devel] Kolab 2.0 Release Coordination

[Richard Bos]

Op woensdag 30 juni 2004 09:23, schreef Stephan Buys:
> - Making Kolab easier to install. Refer to http://dot.kde.org/1088551278/
> where the author basically says Kolab is a Pain In The Ass to setup :-)
>
> Please feed back with other suggestions.

I'm working on this together with Steffen as you may know.  The cvs module 
kolab-webadmin has adapted the autotools build set and it is now possible to 
build that module with ./configure, make, make install or make destdir, etc.

I have a discussion with Steffen about the version and release numbering (I 
must admit that Steffen is happy with the current scheme and that I think 
that it could change ;).  At the moment kolab has a fixed version number 
(defined in configure.ac).  This version number is used to version the 
tarball and rpms.  The rpm file uses the datestamp as its release number.  
This is fine for the rpm, but it does not show up in the tarbal => the result 
is that the tarball and rpm have different versions!

I propose to have use the timestamp in the configure.ac version field (e.g. 
1.90-20040701, I proposed 1.90 to show that it is not an official release.  
Just as suse is doing for kde, see 
http://linux01.gwdg.de/apt4rpm/freshrpms.html#suse91 look for suse-people).  

If this would be done, the tarball as well as rpm will have the same version 
number.  The release tag in the rpm spec file should be set to "1" (e.g.).  

--
Regards,

Richard