[osgeo4w-dev] mapserver/mapscript packages for osgeo4w

Tamas Szekeres szekerest at gmail.com
Wed Feb 5 02:13:38 PST 2014

Is that a preference to have one directory for each project? (I'm not sure
about whether such conveniences exist)
Regarding to qgis we seem to have:

qgis/qgis   - release
qgis/qgis-dev   - development (daily)

Do anyone object to remove/regenerate all the mapserver related stuff for
Or alternatively we can start with x64 first (where no mapserver exists)
and then migrate the layout to x86 if everything is ok?

Best regards,


2014-02-05 Paolo Cavallini <cavallini at faunalia.it>:

> Il 05/02/2014 10:39, Jürgen E. Fischer ha scritto:
> > Having a build server would be a plus and help with more up-to-date
> packages,
> > but it also means a lot of initial work.  It's optional, but still
> requires
> > to redo stuff that's already there.  But if I had a machine and the time
> I
> > would probably jump on it. ;)
> Can't we use our new, powerful QGIS server @Hetzner for this?
> > Mostly the mapserver part - I'd vote for removing all of that - and have
> one
> > stable mapserver package (set) and if necessary a nightly build of trunk
> - just
> > like qgis and qgis-dev.
> big +1 for me
> what prevents us (Tamas) from just go ahead?
> All the best.
> --
> Paolo Cavallini - www.faunalia.eu
> Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html
> _______________________________________________
> osgeo4w-dev mailing list
> osgeo4w-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/osgeo4w-dev/attachments/20140205/64be3dfd/attachment.html>

More information about the osgeo4w-dev mailing list