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:
>
> @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.
--
Greetings, alo
http://www.alobbs.com/
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
