Hi,
I packaged Webware 0.8.1 as a Mandrake RPM for my own use. I still have a few things to do in order to make it robust enough to submit it to Mandrake but at least I can install and remove the core RPM without any trouble. Mandrake convention is to separate the doc and devel RPMs from the core so I am working on how to package the doc RPM properly. The way that Webware is packaged in the tarball with a separate Docs directory per "kit" as opposed to one global Docs directory made it more difficult to package but with the help of a kind fellow on #mandrake, I was able to get it done.
That seems like a lot of work for a handful of kilobytes.
Now, I am working on packaging the Apache modules as distinct modules, mod-webkit and mod-webkit2. Questions:
1. Where should the core Webware directory be installed? I put it in .../python/site-packages/ for lack of a better place. I thought of installing it in /opt or /usr/local but if Webware is packaged as an RPM and available eventually through the Mandrake contribs source, there is no need to put it in there. Besides, site-packages seems to be a good place to put Python packages anyway.
At this point, I don't think it makes sense. Or, you'd have to put it in site-packages/Webware, with a site-packages/Webware.pth file. And some of the names are kind of generic (MiscUtils), and I don't like them being generally visible for all Python programs. I think it's better to put it is /usr/local or something like that -- then that path is added to sys.path when starting the AppServer (but not otherwise).
2. At the moment, MakeAppWorkDir.py needs to be run manually to create one's working directory. I was thinking of running this script from my own RPM and then installing the Apache module and conf files in the appropriate places in /etc/httpd/. I am not completely sure how I would pass parameters to MakeAppWorkDir to create a given working directory and corresponding conf file but I have a few ideas. I have never warmed up to the idea of contexts in Webware and prefer to just have WebKit listening on different ports for different applications. Is that good practice?
That's what I prefer, at least in my own usage. The Webware port makes a default installation and startup script, which is kind of annoying really (or at least distracting), since I am unlikely to use it (and I don't think it's good style to use the main Webware installation as an application). It would be cool to put in a /etc/httpd/log.d/app_server_instance.conf file from MakeAppWorkDir, and then do a Include /etc/httpd/log.d/* (which may already be set up for Mandrake, I don't know it's configuration style).
Any further ideas on how to better package Webware as an RPM would be appreciated.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss
