<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
Hi all,<br>
<br>
Based on the previous proposal I would to discuss the potential
solutions on how to create Debian packages targeting the 8.0
release:<br>
<br>
My suggestion here is to create a Launchpad account for OSGeoLive,
which we will use to "freeze" UbuntuGIS-Unstable when we are
preparing a release. This means that this OSGeoLive ppa will not be
used for packaging, just for release purposes, to avoid last minute
changes in UbuntuGIS-Unstable. <br>
Alternatively we could use UbuntuGIS-Stable and try to keep the
packages we need there, but this would require the OSGeoLive team to
have a certain level of control to that ppa which I am not sure it
is proper. <br></div></blockquote><div><br></div><div>In current UbuntuGIS state I would propose creating Launchpad account for OSGeoLive and freeze rather DEBs there rather than using UbuntuGIS 'stable'.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">1. Use all the standard tools in Debian packaging and create/update
packages on UbuntuGIS ppa.<br>
A VERY simple example to create a deb package is shown here:<br>
<a href="http://ubuntuforums.org/showthread.php?t=910717" target="_blank">http://ubuntuforums.org/showthread.php?t=910717</a><br>
but usually more complex things are required so the complete guides
can be found here:<br>
<a href="https://wiki.debian.org/IntroDebianPackaging" target="_blank">https://wiki.debian.org/IntroDebianPackaging</a><br>
<a href="http://www.debian.org/doc/manuals/maint-guide/" target="_blank">http://www.debian.org/doc/manuals/maint-guide/</a><br>
<a href="http://packaging.ubuntu.com/html/" target="_blank">http://packaging.ubuntu.com/html/</a><br>
<br></div></blockquote><div>This should be a task for Ubuntu or Debian or alternatively packaging projects like UbuntuGIS.<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br><div text="#000000" bgcolor="#FFFFFF">
2. Use helper programs to produce deb packages.<br>
Recently I used this excellent tool for packaging/deployment:<br>
<a href="https://github.com/jordansissel/fpm" target="_blank">https://github.com/jordansissel/fpm</a><br>
<a href="https://github.com/jordansissel/fpm/wiki" target="_blank">https://github.com/jordansissel/fpm/wiki</a><br>
<a href="http://goo.gl/sWs3Z" target="_blank">http://goo.gl/sWs3Z</a><br>
<br>
This actually can save us lots of trouble, especially for building
things that cannot easily be moved to Launchpad.<br>
<br>
Small example to create a GeoServer package:<br>
$ cd /tmp<br>
$ wget
<a href="http://sourceforge.net/projects/geoserver/files/GeoServer/2.4.3/geoserver-2.4.3-war.zip" target="_blank">http://sourceforge.net/projects/geoserver/files/GeoServer/2.4.3/geoserver-2.4.3-war.zip</a><br>
$ unzip geoserver-2.4.3-war.zip<br>
$ mkdir -p /tmp/geoserver-root/var/lib/tomcat6/webapps<br>
$ mv geoserver.war /tmp/geoserver-root/var/lib/tomcat6/webapps/<br>
$ fpm -s dir -t deb -v 2.4.3 -n geoserver -a all -d tomcat6 -C
/tmp/geoserver-root .<br>
<br>
and we have a geoserver_2.4.3_all.deb file ready for us. This also
declares tomcat6 as a dependency and will just deploy the war file
in the correct tomcat folder.<br>
<br>
Then we upload this to our OSGeo apt repository (since we cannot
upload Java binaries to Launchpad) and we simple change the
install_geoserver.sh to apt-get install geoserver. OK, it is a bit
more complicated than this, but you get the picture :)<br>
<br>
FPM also supports translation of Ruby gems and Python packages into
any other format... so it is easy to create deb packages from
pypi...<br></div></blockquote><div><br></div><div>For me FPM tool (os similar approach) looks as the only realistic way for projects like OSGeo Live. It provides very good ratio between price an result. I propose loading core GIS software like GEOS, GDAL, PROJ ... from packaging projects and all others from FPM. Even if I like using Python pis very much, I would propose using FPM also for all Python software to keep centralized approach.<br>
<br></div></div><div class="gmail_quote">Ivan<br></div></div></div>