[Osgeo4w-trac] Re: [osgeo4w] #148: Upgrade MapServer package to 5.6.1 release

[OSGeo4W]

#148: Upgrade MapServer package to 5.6.1 release
---------------------+------------------------------------------------------
Reporter:  jmckenna  |        Owner:  assefa 
    Type:  defect    |       Status:  new    
Priority:  major     |    Component:  Package
 Version:            |   Resolution:         
Keywords:            |  
---------------------+------------------------------------------------------
Comment (by warmerdam):

 One problem with upgrading MapServer to a new version is that there are
 independent packages, such as Python MapScript, that depend on the
 MapServer ABI.  In fact, I think Python MapScript has been broken for more
 than a year because Assefa upgraded the original MapServer package to an
 ABI incompatible version without making arrangements with me.

 With GDAL the practice is to have a distinct package for each ABI version
 (1.5, 1.6, 1.7).  The alternative is to break almost everything on the
 system till all dependent packages are upgraded.

 In the case of MapServer it should be less of an issue.  We would just
 need to ensure that the web applications work with the new mapserver, and
 rebuild a few closely related packages that depend on the ABI (ie. the
 various MapScripts).

 We offer users a guarantee of stability and we have to be very cautious
 about changing packages in a way that a routine update will start breaking
 things.  Even a MapServer update to a new version is likely to do this.

 So, on reflection, I think major new versions of MapServer ought to be
 distinct packages.

 This also comes back to thinking about an OSGeo4W "reboot" where we pick
 new versions for base packages including MapServer, GDAL, Python, etc.

-- 
Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/148#comment:7>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer for the OSGeo stack.