[Kolab-devel] CVS - New Modules and Tools (releng, devel, utils)

[Stuart Bingë]

Hey Steffen,

On Wednesday 12 May 2004 02:08, Steffen Hansen wrote:
> And how do I build a source rpm?

That's not possible at the moment - if you want to do that, you could add 
something like a "%buildsrpm" section in devtool.conf. I intentionally left 
this out as I thought it best to leave the RPM'ing to OpenPKG and leave us to 
concentrate on releasing tarballs.

> > You don't need to uninstall the 'kolab' OpenPKG module, only
> > perl-kolab; as the kolab module contains all these necessary files -
> > templates, config files, etc - you'll need it to be installed. The
> > only difference is, you'll be using the modified 'kolabd' and
> > 'kolabconf' scripts in your checked-out devel module in place of the
> > existing scripts installed with the kolab package. You'll also have
> > to do a '/kolab/etc/rc kolab stop' to shut down the OpenPKG kolab
> > daemon, so that you can run './kolabd' from your devel checkout
> > without an existing kolab daemon running simultaneously.
>
> This currently breaks for me because several config-files are generated
> with stricter permissions or wrong owner. One is session-vars.php and
> the other is imapd.conf (causes an endless loop in cyrus master until
> it fills up the logfile partition).
>
> I did see Stephan's reply to my other mail about the template stuff, and
> I have the most recent stuff from CVS.

If that's the case then there is a problem with the current OpenPKG 2.0 
kolab/perl-kolab release, as the code I imported into CVS was directly from 
OpenPKG. Although, this problem has already been discussed on the list, 
correct?

> Am I just too impatient and try this out at a bad time?
>
> My problem is that I am running behind schedule here. I want to merge my
> stuff in, but can't test it currently and I need to be able to build
> test rpms for our customer and the KDE client developers -- and for
> myself so I can get the remaining new features implemented.
>
> Do you have an estimate on when kolab/perl-kolab stabilizes again?

I must apologise for this then. I've been sidetracked by internal projects and 
my intentions to finally integrate the template code keep on getting 
postponed.

It's actually not that much more to integrate, so I'm going to take today to 
complete it. It is actually way overdue.

> > Please, put it wherever you feel it fits best. As I said, the reason
> > I put it in the releng module was that there are no transformations
> > that need doing in order to get it ready for a release. If it does
> > goes into devel however, we'd have to update the %copydevel section
> > of releng/kolab/devtool.conf to include a "cp ../../devel/kolab/admin
> > ." or whatever, in order to prepare the admin interface for release.
>
> Something like that, yes. A new requirement is a slightly more involved
> install procedure for the webinterface. I want all the included php
> files to reside outside reach of the webserver, and I need a couple of
> other dirs that require special permissions. I imagine something like
> this:
>
> $prefix/var/kolab/www/admin/ <= below this we have webpages,
> 							 stylesheets, images etc.
> $prefix/var/kolab/php/admin/include/ <= php code
>                            /templates/ <= presentation templates
>                            /templates_c/ <= compiled template cache
> 							        needs to be writable by httpd

If the web admin interface is evolving into a complex project on it's own, 
would it perhaps make more sense to create a separate release package for it, 
under releng (as opposed to bundling it in with the Kolab server)?

> Also, the new interface needs PHP Smarty. I checked in an rpm spec file
> for a smarty rpm for openpkg in the server/ module, so that is
> something I need to be able to release also.

With the new CVS structure we should then create a releng/Smarty directory and 
have a devtool.conf in there that can build the Smarty RPM, until such time 
as (if at all) the RPM lands up in OpenPKG.

> > With regards to the version you have - the admin interface in
> > releng/kolab/admin is a verbatim copy of the old
> > server/kolab/kolab/admin, as it stood on 2004-05-03 - I'm not sure if
> > this is the latest version or not?
>
> Doesn't really matter what is there. The new php stuff I have here only
> contains small snippets of the old code. Right now it does about 100%
> of what the old interface does + bugfixes + additional features that we
> need.

OK, I'll leave the admin interface to you then.

Cheers,

-- 
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/