Well, I downloaded and installed it on my 5.1.2 production box; here's what happened:
[root@e-smith home]# rpm -Uvh e-smith-kronolith-1.0-01.noarch.rpm
Preparing... ########################################### [100%]
1:e-smith-kronolith ########################################### [100%]
Bareword found where operator expected at -e line 1, near "s/KRPWD/[long string that looks a lot like my mysql root password]"
syntax error at -e line 1, near "s/KRPWD/[long string that looks a lot like my mysql root password]"
Search pattern not terminated at -e line 1.
Trying to access kronolith, I get this:
DB Error: connect failed
[line 65 of /home/httpd/html/horde/kronolith/lib/Driver/sql.php]
Details have been logged for the administrator.
nothing in error_log, though. It was simple to fix, though; I just changed /home/httpd/html/horde/kronolith/config/conf.php to reflect the correct horde user and password. With that fixed, it seems to work fine as far as I can see at the moment.
Looks like none of the kronolith config files are templated; you've just added a template fragment to the horde registry.
A few suggestions:
* Make the .src.rpm file available. This is required by the GPL anyway, and it'll make it easier for others to track down problems and/or offer improvements.
* Put template fragments in /templates/, not in /templates-custom/. templates-custom is intended only for local customizations.
* From what I can tell from the error message above, you're telling kronolith to use the mysql root user. Really bad idea, for reasons I covered in my HOWTO. Use the horde user instead, with the default horde password (this is the same in 5.5 as in my contribs for 5.1.2, I believe).
* Break this out into 2 RPMs, as Mitel does (and I do)--one for Kronolith itself, and one for the templates and other customizations. The Kronolith RPM can be almost identical to the one at horde.org, just placing the content in /home/httpd instead of /var/www and a couple of other minor changes (you should be able to do this by just changing a couple of the defines at the top of the .spec file if Brent's still building them the way I suggested). The e-smith-kronolith RPM is where you'd put all the template fragments. Tag the release number of that one with your initials (i.e., e-smith-kronolith-1.0-02bm.noarch.rpm or some such).
* Add a template fragment to /home/httpd/html/horde/imp/config/conf.php to give a link for Kronolith from inside IMP (this should be fairly easy with 5.5, but won't be as simple with 5.1.2 and the crappy way I broke up the template). Do the same for turba., and add these two to the kronolith conf.php file as well.
Thanks for taking the time to put this together! I've been meaning to do it for some time, but hadn't gotten around to it.