gwolf at gwolf
Apr 14, 2008, 11:39 AM
Post #1 of 1
(100 views)
Permalink
|
Hi world,
Good news: I finished the 0.6 upgrade scripts, at least to a
reliability point that basically satisfied me ;-) So expect to be able
to install 0.6.1 from apt sometime in the next couple of hours - of
course, for unstable - For the testing distribution, provided no grave
bugs are found, expect a 10 day delay. And for the stable
version... Wait until it stabilizes ;-) It is programmed to be
released around September, so expect it before March ;-)
There are still some points I'd like to forward to you (as a
collective upstream - I've been nagging Álvaro lately, but I cannot
drop all of the work in his hands!)
1- dpkg-shlibdeps is a beautiful tool that helps us auto-generate the
relationships between a given binary and the libraries it is linked
against. Now, dpkg-shlibdeps found that a _huge_ number of
libraries are linked without being used. I'm mostly ignorant in
Cherokee's build process, so I might be doing something
wrong... But I think this comes from further above. This might not
be of utmost importance (i.e. it is a warning, not an error), but
getting the list trimmed down would mean an important footprint
reduction for Cherokee installations made with our packages.
I'm attaching dpkg-shlibdeps' output (shlibdeps) as well as
configure's invocation and output (configure) for further
reference.
2- The man pages are really in a sorry state... I updated some a bit
and wrote a couple more, but only to the most basic coverage
level. Find the patches attached as manpage_additions and
missing_manpages.
3- The fix for the 05to06.py script (for the specific problem I bumped
into) was quite simple. Find the patch attached as fix_05to06.py -
It might not be idiomatically the best, but I know Python
discourages idiomatic use ;-) I'd have loved to just say
«self._vserver_last_priority ||= 1» or something like that, but
hey, I didn't write the goddamn language syntax ;-)
4- This last bit is a bit dirtier, but it solves the problem:
05to06.py operates on single files, but cherokee_admin expects
everything to be integrated. So, I'm integrating the various files
into one... In a hackish and dirty way ;-) I don't want to
disembowel stuff from a couple of scripts, so I'm just attaching
cherokee.preinst (a script that gets run just before Cherokee gets
installed in the system) and config_joiner.
That's it basically... I'm only worried waiting for users to cry about
their beautifully hand-crafted configuration files now ;-) Oh,
BTW... Wouldn't it be sane to include at least a basic login/password
checking in cherokee-admin? I know by default it binds only to
localhost, and it is not expected to be run for more time than what is
strictly needed, but it _is_ a very large hole through which more than
one truck can enter at the wrong time. For a nice plus, enabling SSL
for configuration editing would be most welcome ;-)
--
Gunnar Wolf - gwolf[at]gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
|
configure
