[mapguide-internals] Modify svn:externals for Oem

[Tom Fukushima]

Sounds good.  Thanks Trevor.  BTW, can you also change the CsMap external to point to the 12.01 branch instead of trunk?

Thanks
Tom

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Sunday, April 05, 2009 10:01 PM
To: 'MapGuide Internals Mail List'
Subject: [mapguide-internals] Modify svn:externals for Oem

Hi everyone,

 

I would like to switch the Subversion externals definitions for
http://svn.osgeo.org/mapguide/trunk/MgDev/Oem/ to use relative paths instead
of fully qualified paths.  Currently, the definitions are set as

 

Property svn:externals set to 
CsMap http://svn.osgeo.org/metacrs/csmap/trunk/CsMapDev
fusion http://svn.osgeo.org/fusion/branches/fusion-2.0

 

According to the Subversion docs, relative paths are supported in Svn
versions 1.5 and later.  TortoiseSVN clients based on Svn 1.5 and later
should inherit the same functionality.

http://subversion.tigris.org/svn_1.5_releasenotes.html#externals

 

Property svn:externals set to 
CsMap /metacrs/csmap/trunk/CsMapDev
fusion /fusion/branches/fusion-2.0

 

This should enable us to create read-only Subversion proxies which can
successfully mirror the MapGuide, CsMap, and Fusion vaults.  Without the
change, the proxies will end up hitting the main OSGeo server for any
projects linked using svn:externals.  This is especially problematic for
CsMap which is a 450MB download with all the coordinate system files.

 

Sound good to everyone?

 

Thanks,
Trevor

 

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals