[Kolab-devel] Kolab release confusion

[Stuart Bingë]

> I'm going to upload the structure to CVS within the next two hours or so.

OK, it's in!

I've imported three modules; 'devel', 'releng' and 'utils'. Utils contains the 
various utilities we use (devtool & obmtool), releng contains all the files 
relating to release-engineering and devel is the actual source code.

If you want to develop, just check out 'devel' and start hacking (remember to 
'opa /kolab') and be sure to uninstall the perl-kolab RPM that you're using 
if you want to develop using perl-kolab; as long as the CVS versions of 
Kolab.pm and all other modules are in the current directory (i.e. 
devel/kolab) and you have no other instances of perl-kolab in your PERL 
module path, PERL will load the CVS ones. This means you don't have to keep 
on re-installing RPMs if you want to work on perl-kolab or the daemon; all 
you do is run ./kolabd from devel/kolab, and all your changes will be used. 
All the files assume you have Kolab installed in '/kolab'.

If you want to release then check out 'releng' (as well as 'devel'). There are 
three directories in here; kolab, perl-kolab and obmtool. obmtool contains 
the obmtool.conf that we will use, whereas kolab and perl-kolab contain all 
the files used for creating a Kolab or Perl-Kolab release. In order to 
release you'll have to copy the devtool scripts in 'utils/devtool' to the 
relevant directory, then run './devtool release'. This will copy all the 
source files from devel into their release locations within the current 
directory and roll the necessary tarballs.

Not everything relating to using devtool to release is in; we'll have to 
considerably customise devtool.conf for each module (there are a lot of 
FIXMEs around the place), however for the moment the basics are there. Thanks 
go to Ralf Engelschall and Thomas Lotterer for this release system. (Note 
that you'll need the 'cvs2cl' program in order for the CVS log to 
ChangeLog/Changes functionality to work).

Note that the 'admin' module is now in releng/kolab/admin - even though this 
is considered development code I thought it best to leave it in the kolab 
release directory, as no special transformations are necessary to get it to 
run. Otherwise we'd basically be doing a straight copy from devel to 
releng/kolab in order to roll tarballs.

Another item; the code in here is the latest available from OpenPKG, meaning 
all the changes made to the existing code in CVS are not here. We felt it 
best to use the latest-possible currently released code as a base; from here 
we can merge in the small changes Steffen and the others have made, as well 
as the new template system that we have waiting in the wings (should be 
coming next). The current perl-kolab code in the server module is relatively 
out of sync compared to the code that is available from OpenPKG - I think 
Steffen imported a relatively old release.

Other developers may also want to move some of the directories in the current 
server module over to the new system as well; I'm not sure how everyone feels 
about this though.

Otherwise, enjoy! Comments, etc, are most welcome. Hopefully this will ease 
development for everyone and allow for centralised versioning, eliminating 
the confusion that we've seen in the past.

Regards,

-- 
Stuart Bingë
Code Fusion cc.

Office: +27 11 673 0411
Mobile: +27 83 298 9727
Email: s.binge at codefusion.co.za

Tailored email solutions; Kolab specialists.
http://www.codefusion.co.za/