<html>
<head>
<style type="text/css">
<!--
body { margin-right: 4px; font-variant: normal; margin-left: 4px; margin-bottom: 1px; line-height: normal; margin-top: 4px }
p { margin-bottom: 0; margin-top: 0 }
-->
</style>
</head>
<body style="margin-right: 4px; margin-left: 4px; margin-bottom: 1px; margin-top: 4px">
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">All,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Is there likely to be any difference in the packaging of things? I mean, this package development has been a long time coming in my mind, and having it originate from within the Mapserver dev community would seem to want to push a generally tighter integration than has been previously attempted. I guess my aim would be to make things tighter package wise.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Although upon reflection, maybe what's really needed is a very (very) tight package for a default install, with various optional package linking/include pipelines.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">???</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> Daniel Morissette <dmorissette@mapgears.com> wrote:<br> </p>
<div style="margin-right: 0; border-left: solid 1px #050505; background-color: #f3f3f3; margin-left: 15px; margin-bottom: 0; padding-left: 7px; margin-top: 0">
<p style="margin-bottom: 0; margin-top: 0">
I agree as well, but perhaps not all in a single deb/rpm package, i.e.<br>with separate selectable packages for the core binaries, support files,<br>docs and sample datasets, so that those who only want the CGI can still<br>install only that. I believe that's already the way we handle the<br>various mapscript flavors vs the CGI in UbuntuGIS, and other distros for<br>instance.<br><br><br>Lime, Steve D (DNR) wrote:<br>> I like it. It's a whole new way to get contributors in the door as well... Steve<br>><br>> -----Original Message-----<br>> From: mapserver-dev-bounces@lists.osgeo.org [mailto:mapserver-dev-bounces@lists.osgeo.org] On Behalf Of Paul Ramsey<br>> Sent: Monday, September 27, 2010 4:29 PM<br>> To: MapServer Dev List<br>> Subject: [mapserver-dev] Out of Box MapServer<br>><br>> Daniel is trying to avoid scope creep in his simple viewing thread, so<br>> I'm going to start a new one.<br>><br>> I think the main reason there isn't a good "out of the box" MapServer<br>> experience yet is because there is no 'make install' target. Weird<br>> hey?<br>><br>> If there was a 'make install' you could install the CGI directly into<br>> cgi-bin, and install support files, like a standard set of styles, a<br>> standard set of fonts, some standard templates, some basic data, even<br>> some HTML files with documentation and whatnot. Linux packagers could<br>> then say to themselves, "OK, I will have the etc directory be this on,<br>> the share directory be this one, I'll drop the CGI into the system CGI<br>> directory here, and now I am set to build an RPM/DEB/whatever". Other<br>> OSes would do similar stuff, and each copy of MapServer would have a<br>> similar expectation of "what-is-expected-to-exist-by-default".<br>><br>> Once you have something more than the CGI available being installed by<br>> default, the amount of user-friendliness you can implement across all<br>> platforms goes up quite quickly.<br>><br>> For exampleness, 'make install' for example on RHEL<br>><br>> /var/www/cgi-bin/mapserv<br>> /var/www/htdocs/mapserver/docs<br>> /var/www/htdocs/mapserver/examples<br>> /etc/mapserv.conf<br>> /usr/share/mapserver<br>> /usr/share/mapserver/symbols<br>> /usr/share/mapserver/fonts<br>> /usr/share/mapserver/templates<br>> /usr/share/mapserver/data<br>> /usr/docs/mapserver<br>><br>> What do you think?<br>><br>> Paul<br>> _______________________________________________<br>> mapserver-dev mailing list<br>> mapserver-dev@lists.osgeo.org<br>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver">http://lists.osgeo.org/mailman/listinfo/mapserver</a>-dev<br>><br>><br>> _______________________________________________<br>> mapserver-dev mailing list<br>> mapserver-dev@lists.osgeo.org<br>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver">http://lists.osgeo.org/mailman/listinfo/mapserver</a>-dev<br><br><br>--<br>Daniel Morissette<br><a href="http://www.mapgears.com/">http://www.mapgears.com/</a><br>_______________________________________________<br>mapserver-dev mailing list<br>mapserver-dev@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/mapserver">http://lists.osgeo.org/mailman/listinfo/mapserver</a>-dev<br>
</p>
</div>
</body>
</html>