Re: Debian still shipping 0.7.x
Beech Rintoul <beech <at> alaskaparadise.com>
2008-09-02 19:01:44 GMT
On Tuesday 02 September 2008, Alvaro Lopez Ortega said:
> Beech Rintoul wrote:
> > On Monday 01 September 2008, Gunnar Wolf said:
> >> As I said, there were several pitfalls for 0.5->0.7 upgrades,
> >> and some other Debian policy aspects I had not taken care of
> >> (i.e. byte-compiling the Python modules for the administrative
> >> interface upon installation).
> >
> > I would like to see Cherokee incorporate this into their install.
> > Compiling by starting the admin binary isn't an option for a
> > FreeBSD install so I did the following:
> >
> > <at> cd ${DATADIR}/admin && ${FIND} . -name "*.py" |\
> > ${XARGS} ${PYTHON_CMD} ${PYTHON_LIBDIR}/py_compile.py
> >
> > I would imagine that this is also an issue with other dists.
>
> It is a known issue, actually:
>
> http://code.google.com/p/cherokee/issues/detail?id=79
>
> When I first looked at it, I was not sure about how it should be
> fixed, actually. The main issue is that even if the Automake
> Python support does everything for us (byte-compiling, pyc files
> clean up and so on), it tries to install cherokee-admin as a Python
> module rather than in its target directory (usually
> /usr/share/cherokee/admin).
>
> Have you guys experience with this? I would only agree on adding
> the manual clean up command if there is no way to point Automake to
> use the 'right' installation path. Otherwise it'd be much cleaner
> to relay on Automake for this stuff.
I ran into exactly that problem with our py install software, hence
the extra step. Our problem was after a user ran the admin binary and
then deinstalled the port there were about 20 .pyc files left behind.
I could have put a check and some makefile magic to deal with that,
but it was easier just to byte compile the .py files and be done with
it.
As for automake dealing with it, I'm not sure if it's capable of that,
but having the application use the default install path as a target
would be ok. We have to patch the paths anyway because our path is
slightly different than the linux dists (/usr/local/share).
I did look at several py ports to see if there was an easier way to
compile that directory, but our system is set up to deal with that as
a python module also, so byte compiling after install was my only
option.
That being said, after some tweaking I moved 0.8x to our main port and
except for a couple of minor issues (fixed) our users are very happy
with it. I also removed the -devel version because I didn't feel it
was needed anymore. We are also about to go into a code freeze for
the new releases and I wanted to make sure Cherokee-0.8 was included.
The only other request I've been getting is to make the admin install
optional for users who already have cherokee installed or want to
configure by hand. I haven't looked at that closely, but I don't
remember seeing a --with-cherokee-admin knob. So that may take a bit
of work.
Beech
--
--
---------------------------------------------------------------------------------------
Beech Rintoul - Sys. Administrator - beech <at> alaskaparadise.com
/"\ ASCII Ribbon Campaign | Alaska Paradise
\ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310
X - NO Word docs in e-mail | Anchorage, AK 99501
/ \ - Please visit Alaska Paradise - http://www.alaskaparadise.com
---------------------------------------------------------------------------------------
RSS Feed