[osgeo4w-dev] [osgeo4w] #473: create a geos-c++ package

[OSGeo4W]

#473: create a geos-c++ package
------------------------+----------------------------
Reporter:  rashadkm     |       Owner:  osgeo4w-dev@…
    Type:  enhancement  |      Status:  new
Priority:  major        |   Component:  Package
 Version:               |  Resolution:
Keywords:               |
------------------------+----------------------------

Comment (by jef):

 Replying to [comment:8 rashadkm]:
 > Replying to [comment:7 jef]:
 > > > Is it possible to isolate these stuff in seperate directories in the
 server.
 > > >
 > > > msvc2010/{x86,x64}/ossim,geos,otb,qt,
 > > > msvc2013/{x86,x64}/ossim,geos,otb,qt
 > >
 > > Um, who's going to produce all those packages?
 >
 > Same packagers who are uploading packages now. Except that there is an
 option to produce binaries for specific compilers.

 That could already be done by embedding the compiler version into the
 package name, which would also be required to manage the dependencies.
 But it's doesn't seem worthwhile to me.  What's the gain?   OSGeo4W is
 mainly to make applications available to the users, which probably
 wouldn't see the benefit of being able to choose from builds from myriads
 of compilers either (why stop with 2013?).

 > > > If msvc2013 or 2015 have not much packages... then that is not a
 problem. It will arrive later.
 > > > ...
 > >
 > > Sorry I don't follow.
 >
 > I was saying if not all packages are not available for msvc2013 or
 something else. That can be rebuild from the existing package source.
 Right ?

 Packages are built manually - at least there currently is no requirement
 to upload sources in some standardized way to make the automated
 production of packages possible - let alone for multiple compiler
 versions.

--
Ticket URL: <https://trac.osgeo.org/osgeo4w/ticket/473#comment:9>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.