<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>We had this on our todo for 3.0 (thought can't find the ticket at moment) to not require same dependencies as postgis for the command line tools. I think we resolved some but not all to make this a reality and to allow configure to just build the commandline tools.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>That said when we are done with that what we can in theory have in a perfect scenario<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>For reference see - <a href="https://trac.osgeo.org/postgis/ticket/4260">https://trac.osgeo.org/postgis/ticket/4260</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>shp2pgsql -> relies on nothing (possibly liblwgeom though) – I'd like to just make that static and not sure we got to that point. It just outputs an sql script so has no need for libpq or anthing PostgreSQLy<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>pgsql2shp -> relies on liblwgeom (in theory any geos/proj stuff needed would be done in the SQL calls so no need to have the commandline need those.) / libpq <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>raster2pgsql -> gdal, liblwgeom (?) again this makes no interaction with PostgreSQL as I recall, just spits out an sql script that is normally piped to psql.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I think prior versions had some unnecessary includes in the files for these that brought in unnecessary dependencies.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Hope that helps,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> postgis-devel [mailto:postgis-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Adam Dadvar<br><b>Sent:</b> Friday, May 10, 2019 7:38 AM<br><b>To:</b> PostGIS Development Discussion <postgis-devel@lists.osgeo.org><br><b>Subject:</b> Re: [postgis-devel] Docker and Lightweight Libraries<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>Hi,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><i>"We build images for CI where we build all the dependencies but</i><o:p></o:p></p></div><p class=MsoNormal><i>postgis (<a href="https://cloud.docker.com/u/postgis/repository/docker/postgis/postgis-build-env" target="_blank">https://cloud.docker.com/u/postgis/repository/docker/postgis/postgis-build-env</a>)<br>but not for distribution." </i><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Makes sense to use it for CI, again was mostly just wondering about distribution, would be good to get people's thoughts on setting one up.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><i>"I'm not sure what bash scripts you are refering too, but this looks<br>like a packaging request/issue."</i><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Sorry, I should have been more clear.<o:p></o:p></p></div><div><p class=MsoNormal>The bash script I'm referring to is <i>shp2pgsql, </i>I left it plural because I wasn't sure if there are any other PostGIS commands that are executable from the terminal.<o:p></o:p></p></div><div><p class=MsoNormal>This is more a packaging request yes. I'll admit I'm not sure on the dependencies within PostGIS, so it may be that even just for <i>shp2pgsql</i> requires a lot of these dependencies, just wanted to float the idea and if we can foresee a large amount of disk savings then maybe it is worth the effort.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><i>"One note, the packages I build locally<br>including everything (binaries and libraries with full debug symbols,<br>update scripts...) take ~43MB so something looks suspicious in your<br>300MB library."</i> <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The 300MB footprint I'm talking about is the fact that if I remove PostGIS from my machine (Fedora 29 with postgreSQL client only) I get 360MB of freed space:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>$ dnf remove postgis<o:p></o:p></p></div><div><div><p class=MsoNormal>Transaction Summary<o:p></o:p></p></div><div><p class=MsoNormal>======================<o:p></o:p></p></div><div><p class=MsoNormal>Remove 33 Packages<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Freed space: 360 M<o:p></o:p></p></div><div><p class=MsoNormal>Is this ok [y/N]:<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Obviously this is mostly from the other libraries, but I was just wondering if there was any way that a smaller client-only version could be created.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Adam<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><p class=MsoNormal>On Fri, 10 May 2019 at 11:56, Raúl Marín Rodríguez <<a href="mailto:rmrodriguez@carto.com">rmrodriguez@carto.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>Hi,<br><br>> Have been playing around with Docker a lot recently and was wondering if there was any reason why there is no official PostGIS Docker repository that builds on the PostgreSQL image?<br><br>We build images for CI where we build all the dependencies but<br>postgis (<a href="https://cloud.docker.com/u/postgis/repository/docker/postgis/postgis-build-env" target="_blank">https://cloud.docker.com/u/postgis/repository/docker/postgis/postgis-build-env</a>)<br>but not for distribution.<br><br>> While we're on the subject of Docker and containers, I thought I'd ask if there is any scope for a lightweight PostGIS library that only has the bash scripts in it? A sort of "postgis-client" type of thing, that allows you to interact with remote databases running PostGIS without having to install the entire 300MB library yourself.<br><br>I'm not sure what bash scripts you are refering too, but this looks<br>like a packaging request/issue. One note, the packages I build locally<br>including everything (binaries and libraries with full debug symbols,<br>update scripts...) take ~43MB so something looks suspicious in your<br>300MB library.<br><br>Regards<br>-- <br>Raúl Marín Rodríguez<br><a href="http://carto.com" target="_blank">carto.com</a><br>_______________________________________________<br>postgis-devel mailing list<br><a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><o:p></o:p></p></blockquote></div></div></div></div></div></div></body></html>