Hi guys,
First of all, keep up with the good work! Cherokee is getting greater
every
day!
Some time ago I bitched about the debian packages not firing the config
converter and I stand corrected cause it actually does. My config files were
converted correctly.
Today I updated to the newest release (0.99.2.1) and I run into some
problems. First of all, apt-get didn't update the packages correctly, I had
to manually add the different packages in the correct order. But I ran into
problems with the libcherokee-server0 one. It depends on libavcodec51 but my
system had libavcodec52 (3:0.svn20090204-3). Funny enough, it didn't identify
that one as current and still demanded the old version so I had to manually
install it from launchpad.net. Is that right? Shouldn't it work with the
latest package?
And just as a side note, I have another little problem. Every time I
update
the deb package, it asks me if I want the new config file. Running a diff
against both I can see some minor changes, but it's a pain in the ass to
check all and incorporate them into my config file as I have shit ton of
virtual rules. If the config got separated into 2 files, my virtual domain
rules + regular config (ports, etc.) it would be much easier to update. I'm
pretty sure there are reasons that have lead to not doing this (excesive
config fragmentation, don't listen to lazy users like me, etc.) but I wonder
what u guys think about the idea, pros? cons?
My 2 cents :)
Alex
--
http://www.neurosecurity.com
"We must be the change we wish to see in the world"
Mahatma Gandhi
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
