CentOS packaging (was Re: [geonode] GeoNode deployment on CentOS 5:
one should use python26-mod_wsgi)
- Mathieu Baudier
- 2010-12-13 @ 21:38
> I've updated the sources on Github so you can take a look there; the
> corrected docs will be posted for the next release (1.0 if no more
> high-severity bugs are found).
Sorry I had missed your answer, so I did not review the sources on
github before 1.0 :(
There is actually a typo here:
It should be python26-mod_wsgi and not python26_mod_wsgi
Moreover, meanwhile EPEL has packaged python26-mod_wsgi (I had asked
in on the mailing-list, so I don't know if it is related).
Our policy by ELGIS is to rather have the software maintained by EPEL
rather than by us, so that they have a wider audience. Our mission is
to have the latest GIS software running on Enterprise Linux, so we are
more of a stopgap when EPEL cannot keep up the pace :).
Some people on the EPEL list also suggested to me that repackaging
python26-virtualenv was unnecessary and that EPEL's virtualenv would
have done the job, provided python26 is available.
So, I think that we should go to another round of testing with GeoNode
1.0 and it would probably be possible to simplify the deployment
instructions for CentOS.
Anyhow, I saw on the GeoNode 1.0 release page:
that you were planning to provide packages for CentOS.
We are available if we can help with the packaging or the testing!
We are currently working hard to provide a proper packaging of GIS
java apps on CentOS (currently struggling with imageio-ext and other
low-level JNI stuff).
Our goal is to be able to properly package GeoServer, GeoNetwork etc.
(and of course GeoNode :)
Meanwhile, I'd be interested in having a rougher deployment, with the
WAR files part of the distribution. I'd be happy to discuss it with
people interested/involved in this CentOS packaging.
Last but not least: congratulations for the GeoNode 1.0 release!
Re: CentOS packaging (was Re: [geonode] GeoNode deployment on CentOS
5: one should use python26-mod_wsgi)
- David Winslow
- 2010-12-13 @ 21:59
could not decode message