Alvaro Lopez Ortega dijo [Mon, Dec 13, 2010 at 09:39:11PM +0100]: > ========================= > Cherokee 1.0.14 released! > =========================
Great news! :-D
And, as I had not done since 1.0.8, I am preparing a Debian upload -
Not yet to the regular "unstable" distribution, as we are in deep
freeze now and really want to avoid anything that makes it harder for
a clean process. I am making the upload to the "experimental"
distribution instead (see below for details). I was on
something-similar-to-a-vacation-but-loaded-with-work due to... Work
reasons ;-)
Still, five releases are many releases, and it's time to do an upload
- Besides, I even got a bug report asking for the upload ;-) So, here
it goes.
Now, there are several changes to Cherokee which I need to process,
understand, incorporate. The main one (from a packager's point of
view) is the demise of libcherokee-config0 - Personally, I am happy
of this, as it introduced a dependency loop. Still, I want to
understand a couple of things - Please note that I am anyway uploading
the package to Experimental (as there is a reason for it being
experimental ;-) ), so _there_might_be_breakages_. You have been
warned.
When Álvaro and me did the initial packaging, and throughout
Cherokee's evolution over the years, we have tried to
compartamentalize as much as possible the built components, in order
to allow installations to be as minimal as possible: No need i.e. for
installing the MySQL backend or the multimedia streaming module in an
embedded device.
Until 1.0.8-4, we shipped two library packages for configuration
handling: libcherokee-config0 and libcherokee-config-dev. As of 1.0.9,
Leonel noticed (for the Ubuntu builds)
/usr/lib/libcherokee-config.so.* went missing - So he disabled the
build of the libcherokee-config-dev package. But today, working on the
new packages, I found that the only remaining files in the
libcherokee-config0 package were Python scripts, PNG images and the
like - Which should have been part of the administration package
anyway... So I moved it all to the libcherokee-mod-admin package and
killed both of the libcherokee-config ones.
( while working on this mail, I had a quick chat with Álvaro - He
basically confirmed me this last point, and suggested me to rename
libcherokee-mod-admin to cherokee-admin, which I am doing)
Anyway, us Debianers are at the end of a ~2yr cycle and close to
releasing a new OS version, and at the beginning of another such
cycle. So, any deriver (specially Leonel, who does the Ubuntu
highly-experimental PPA stuff), please triple-check everything works
as expected. As for the rest of the world, I will keep suggesting to
use the Stable release wherever possible, then the Testing and
Unstable releases if you _really_ need them, and if you want to cry a
bit, try with Experimental stuff ;-)
How to use experimental?
========================
Ok, so you really want to use Experimental? Good. First thing first:
Proper documentation available [2]. I will only outline the VERY basic
steps to do it.
• Add the following line (replacing with your closest mirror, if you
prefer) to your /etc/apt/sources.list:
deb http://ftp.debian.org/debian experimental main
• Don't worry, it will not pull in _all_ of experimental. Experimental
has a very low priority, so your system will not become Windows
Vista :-P
• apt-get update
• apt-get -t experimental install cherokee
That should do. Oh, and of course — As I am introducing changes in the
packages list and names, this new Cherokee version will have to go
through the NEW queue (as if it were a new package). You might have to
wait a couple of days to get it. If I have some time off for it, I
will provide (and post to this list) a link to get the releases from
while the NEW queue is processed.
Greetings,
--
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606865
[2] http://wiki.debian.org/DebianExperimental
signature.asc
Description: Digital signature
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
