[mapserver-dev] Out of Box MapServer

[Bob Basques]

All, 

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. 

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. 

??? 

bobb 



>>> Daniel Morissette <dmorissette at mapgears.com> wrote:

I agree as well, but perhaps not all in a single deb/rpm package, i.e.
with separate selectable packages for the core binaries, support files,
docs and sample datasets, so that those who only want the CGI can still
install only that. I believe that's already the way we handle the
various mapscript flavors vs the CGI in UbuntuGIS, and other distros for
instance.


Lime, Steve D (DNR) wrote:
> I like it. It's a whole new way to get contributors in the door as well... Steve
>
> -----Original Message-----
> From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
> Sent: Monday, September 27, 2010 4:29 PM
> To: MapServer Dev List
> Subject: [mapserver-dev] Out of Box MapServer
>
> Daniel is trying to avoid scope creep in his simple viewing thread, so
> I'm going to start a new one.
>
> I think the main reason there isn't a good "out of the box" MapServer
> experience yet is because there is no 'make install' target. Weird
> hey?
>
> If there was a 'make install' you could install the CGI directly into
> cgi-bin, and install support files, like a standard set of styles, a
> standard set of fonts, some standard templates, some basic data, even
> some HTML files with documentation and whatnot. Linux packagers could
> then say to themselves, "OK, I will have the etc directory be this on,
> the share directory be this one, I'll drop the CGI into the system CGI
> directory here, and now I am set to build an RPM/DEB/whatever". Other
> OSes would do similar stuff, and each copy of MapServer would have a
> similar expectation of "what-is-expected-to-exist-by-default".
>
> Once you have something more than the CGI available being installed by
> default, the amount of user-friendliness you can implement across all
> platforms goes up quite quickly.
>
> For exampleness, 'make install' for example on RHEL
>
> /var/www/cgi-bin/mapserv
> /var/www/htdocs/mapserver/docs
> /var/www/htdocs/mapserver/examples
> /etc/mapserv.conf
> /usr/share/mapserver
> /usr/share/mapserver/symbols
> /usr/share/mapserver/fonts
> /usr/share/mapserver/templates
> /usr/share/mapserver/data
> /usr/docs/mapserver
>
> What do you think?
>
> Paul
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev


--
Daniel Morissette
http://www.mapgears.com/
_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20100927/58903392/attachment.html