mapguide-2.0.2.3011.tar.gz

[pcardinal]

OS: Windows XP and Windows Vista Unzipping utilities : WinRar and WinZip How come there is so many errors when unzipping mapguide-2.0.2.3011.tar.gz? Example: twice the file "mov" in \mapguide-2.0.2.3011\mapguide-2.0.2\Oem\fusionframework\fusion\trunk\templates\mapguide\slate\theme\default\img with two different sizes. Where can I find a good zip file? Pierre

[Tom Fukushima]

If you can't get around the problem with unzipping these files on Windows, I suggest getting the source directly from subversion using the tags/MAPGUIDE2.0.2 tag.  The source will not have the correct version stamps in the files but perhaps someone who knows off hand can describe how to set these correctly.

The subversion location is http://svn.osgeo.org/mapguide/tags/MAPGUIDE2.0.2.



-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of pcardinal
Sent: Tuesday, August 11, 2009 9:11 AM
To: [hidden email]
Subject: [mapguide-internals] mapguide-2.0.2.3011.tar.gz


OS: Windows XP and Windows Vista

Unzipping utilities : WinRar and WinZip

How come there is so many errors when unzipping mapguide-2.0.2.3011.tar.gz?

Example:

twice the file "mov" in
\mapguide-2.0.2.3011\mapguide-2.0.2\Oem\fusionframework\fusion\trunk\templates\mapguide\slate\theme\default\img
with two different sizes.

Where can I find a good zip file?

Pierre
--
View this message in context: http://n2.nabble.com/mapguide-2.0.2.3011.tar.gz-tp3424462p3424462.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Jason Birch]

We should probably update the build instructions to reference SVN instead of the TAR file.  It's way easier that way for developers to contribute patches back to the project, indicate what file they're having problems with, etc.

Pierre, there's a VBS utility in the trunk of MgDev that allows you to set the version number prior to compiling.  It requires Collabnet SVN (or another command line SVN tool) on the path.  Running it will give you the syntax, but it's basically:

cscript updateversion.vbs /major:2 /minor:1 /point:0

You can download it by clicking on the "Original Format" link at the bottom of this page:

http://trac.osgeo.org/mapguide/browser/trunk/MgDev/updateversion.vbs

I'd also recommend using MapGuide 2.1 branch at this point over 2.0.x.  It's more stable and faster.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: Tuesday, August 11, 2009 11:16 AM
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz

If you can't get around the problem with unzipping these files on Windows, I suggest getting the source directly from subversion using the tags/MAPGUIDE2.0.2 tag.  The source will not have the correct version stamps in the files but perhaps someone who knows off hand can describe how to set these correctly.

The subversion location is http://svn.osgeo.org/mapguide/tags/MAPGUIDE2.0.2.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Tom Fukushima]

Good catch.  If someone would edit this open office document and send it back to me, I can post it for 2.1:
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/BuildingAndConfiguringMGOSOnWindows.odt

Here are some other documents that could probably use updates:
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/BuildingAndConfiguringMGOSOnLinux.odt
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/GettingStarted.odt

Thanks
Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Tuesday, August 11, 2009 12:34 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz

We should probably update the build instructions to reference SVN instead of the TAR file.  It's way easier that way for developers to contribute patches back to the project, indicate what file they're having problems with, etc.

Pierre, there's a VBS utility in the trunk of MgDev that allows you to set the version number prior to compiling.  It requires Collabnet SVN (or another command line SVN tool) on the path.  Running it will give you the syntax, but it's basically:

cscript updateversion.vbs /major:2 /minor:1 /point:0

You can download it by clicking on the "Original Format" link at the bottom of this page:

http://trac.osgeo.org/mapguide/browser/trunk/MgDev/updateversion.vbs

I'd also recommend using MapGuide 2.1 branch at this point over 2.0.x.  It's more stable and faster.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: Tuesday, August 11, 2009 11:16 AM
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz

If you can't get around the problem with unzipping these files on Windows, I suggest getting the source directly from subversion using the tags/MAPGUIDE2.0.2 tag.  The source will not have the correct version stamps in the files but perhaps someone who knows off hand can describe how to set these correctly.

The subversion location is http://svn.osgeo.org/mapguide/tags/MAPGUIDE2.0.2.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Jason Birch]

Tom, do you think it would make sense to maintain these in the wiki instead of as offline documents?  That way more users would be able to collaborate on them and improve user experience.  Right now, we have those and a bunch of outdated build tutorials sitting on the OSGeo wiki.  I would personally prefer to see all of this information in Trac, properly organised.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: Tuesday, August 11, 2009 11:42 AM
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz

Good catch.  If someone would edit this open office document and send it back to me, I can post it for 2.1:
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/BuildingAndConfiguringMGOSOnWindows.odt

Here are some other documents that could probably use updates:
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/BuildingAndConfiguringMGOSOnLinux.odt
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/GettingStarted.odt
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Tom Fukushima]

Yes, that would be fine with me.  I think that the original impetus for putting them in PDF was because that was the way that the Autodesk tech pubs created them; since the MGOS community will maintain them, putting them on the wiki sounds like the right thing to do.


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Tuesday, August 11, 2009 2:24 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz

Tom, do you think it would make sense to maintain these in the wiki instead of as offline documents?  That way more users would be able to collaborate on them and improve user experience.  Right now, we have those and a bunch of outdated build tutorials sitting on the OSGeo wiki.  I would personally prefer to see all of this information in Trac, properly organised.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: Tuesday, August 11, 2009 11:42 AM
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz

Good catch.  If someone would edit this open office document and send it back to me, I can post it for 2.1:
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/BuildingAndConfiguringMGOSOnWindows.odt

Here are some other documents that could probably use updates:
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/BuildingAndConfiguringMGOSOnLinux.odt
http://mapguide.osgeo.org/sites/mapguide.osgeo.org/files/GettingStarted.odt
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[pcardinal]

You're right about SVN but I am following the advice in the build.bat under trunk\MgDev

...
rem For a "cleaner" build experience, run this script from an exported copy of the
rem MapGuide source code (ie. without subversion folders).
...


Does my understanding is wrong about trying to use the file mapguide-2.0.2.3011.tar.gz?

Effectively I rather use 2.1

Pierre

Jason Birch wrote:

We should probably update the build instructions to reference SVN instead of the TAR file.  It's way easier that way for developers to contribute patches back to the project, indicate what file they're having problems with, etc.

Pierre, there's a VBS utility in the trunk of MgDev that allows you to set the version number prior to compiling.  It requires Collabnet SVN (or another command line SVN tool) on the path.  Running it will give you the syntax, but it's basically:

cscript updateversion.vbs /major:2 /minor:1 /point:0

You can download it by clicking on the "Original Format" link at the bottom of this page:

http://trac.osgeo.org/mapguide/browser/trunk/MgDev/updateversion.vbs

I'd also recommend using MapGuide 2.1 branch at this point over 2.0.x.  It's more stable and faster.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: Tuesday, August 11, 2009 11:16 AM
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz

If you can't get around the problem with unzipping these files on Windows, I suggest getting the source directly from subversion using the tags/MAPGUIDE2.0.2 tag.  The source will not have the correct version stamps in the files but perhaps someone who knows off hand can describe how to set these correctly.

The subversion location is http://svn.osgeo.org/mapguide/tags/MAPGUIDE2.0.2.
_______________________________________________
mapguide-internals mailing list
[e-mail]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Jason Birch]

Ah...

I believe that's referring to the "svn export" command.  It basically copies all of the files into a different location but without the .svn directories.

The new windows build scripts (build.bat) allow you to build in place and then "install" into a clean directory structure.  I personally prefer this approach, as it means that I'm always building from a "live" location.

The "clean" action on the build script is pretty decent, but if I need a really clean environment I just
use the Perl svn-clean script (1) which removes all files that aren't under version control.  Have to be careful with this though if you're doing any new development as it can blow away your new local files.

1. svn-clean: http://svn.collab.net/repos/svn/trunk/contrib/client-side/svn-clean

Jason

-----Original Message-----
From: pcardinal
Sent: Tuesday, August 11, 2009 3:17 PM
Subject: RE: [mapguide-internals] mapguide-2.0.2.3011.tar.gz


You're right about SVN but I am following the advice in the build.bat under
trunk\MgDev

...
rem For a "cleaner" build experience, run this script from an exported copy
of the
rem MapGuide source code (ie. without subversion folders).
...


Does my understanding is wrong about trying to use the file
mapguide-2.0.2.3011.tar.gz?

Effectively I rather use 2.1
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals