[Kolab-devel] CVS structure (upload of CF engine)
Stephan Buys
list at codefusion.co.za
Tue Apr 6 10:29:06 CEST 2004
Hi all,
We want to upload our work to CVS, but unfortunately the structures of the packages
differ widely.
The way we do things is that we have two folders called devel and releng.
devel contains all the perl source files, which makes it easy to check out from CVS
and start coding without hassle...
the releng directory contains all the packaging/release related materials. (Like perl
distro manifests, spec files, etc.)
The fact that the code depends heavily on perl-kolab has prompted us to go this way.
Problems with the current CVS structure:
1) The folders apache, imapd, perl-kolab, proftpd, db, horde, openldap, postfix and sasl
should not be there. The patches in there have been integrated into OpenPKG and should
be maintained using the OpenPKG mechanism in the future...
2) There are badly outdated files and scripts in doc (these could be archived)
3) obmtool.conf, obmtool should be moved to the utilities folder, if kept here at all...
4) The current scripts in the utilities folder can be archived...
We would then like to add:
1) releng (which contains the release/package files for the daemon, interfaces and perl-kolab)
2) devel (which contain the sourcecode for development purposes. perl-kolab, engine, and admin
source will then be stored there...)
Any thoughts or feedback?
Regards,
--
Stephan Buys
Code Fusion cc.
Tel: +27 11 391 1412
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za
E-mail Solutions, Kolab Specialists.
http://www.codefusion.co.za
More information about the devel
mailing list