[fdo-trac] #5: GDAL: Update FDO Thirdparty to latest GDAL Source

[FDO]

#5: GDAL: Update FDO Thirdparty to latest GDAL Source
-----------------------------------+----------------------------------------
 Reporter:  gregboone              |         Owner:  gregboone
     Type:  enhancement            |        Status:  assigned 
 Priority:  minor                  |     Milestone:  3.3.0    
Component:  Thirdparty Components  |       Version:           
 Severity:  2                      |    Resolution:           
 Keywords:  GDAL WMS               |   External_id:           
-----------------------------------+----------------------------------------
Comment (by anonymous):

 I will update the ticket to indicate that this is a Thirdparty Components
 issue.

 As for your idea that we remove GDAL from Thirdparty, I am hesitant to do
 this without a larger plan in place on how we deal with Thirdparty
 components in general. Bob has mentioned a need to develop a common FDO/MG
 plan that would mitigate the need to keep third-party source code in our
 repository. MapGuide has similar issues with their Thirdparty components.

 Your idea on having the build process pull GDAL from the GDAL SVN is a
 valid alternative, but I have some concerns on the impact. Such a change
 would shift the responsibility for obtaining a compatible set of GDAL
 source files compatible with our providers from the FDO development team
 to the FDO runtime build process. While it would introduce flexibility, it
 would leave the user without a default mechanism in place to get a build
 going quickly without having to worry about the specifics of pulling the
 code from a separate SVN.

 I propose an alternative to your proposal...

 - Update the default version of GDAL in Thirdparty to 1.4.x
 - Add an $FDOGDAL variable to the build process (Similar to $FDO) that
 identifies where the GDAL source is located. The default value of this
 variable would point to the Thirdparty/GDAL location. The user has the
 option to change the value of this variable to point to a different copy
 of GDAL. This approach would be similar (but not identical) to how we
 handle ODBC and MYSQL SDK components.
 - Add an option to the WMS and GDAL configure scripts that allow the user
 to specify the GDAL source code location as a --with option.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/5#comment:5>
FDO <http://fdo.osgeo.org/>
Feature Data Objects