[fdo-internals] Using new SVN for PostGIS

[Greg Boone]

Fundamentally, if you want to be officially 'integrated' with the build
of FDO that is supported in Map Hammerhead then you will have to drop
your changes in branches/3.2.x. (NOTE: You would also be required to
merge your changes into the trunk) 

However, submitting into branches/3.2.x requires additional due
diligence. Does your submission affect any existing fdocore/fdordbms
*Windows* build processes, existing header files or source files? If so,
these files will need to be dropped ASAP using the Map/FDO defect
tracking/code submission mechanism. 

If such changes are required send me the set of fdocore/fdordbms
existing/new files to be modified (as a zip file) and Robert and I will
determine the effect of making such changes. We will also determine if
the map team is willing to take these changes at this time. Once that
determination is made you would be free to integrate your changes.

If you drop only into the trunk and not the 3.2.x branch then we would
not be able to guarantee that the PostGIS provider would be supported
inside Map using FDO 3.2.x without further testing. Actually, I
seriously doubt that you would be supported in Hammerhead due to the Dec
18th change made by Brent Robinson

"Binary compatibility change to fdo.dll (trunk version)"

See attached file for details.

Greg

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Mateusz
Loskot
Sent: Tuesday, January 16, 2007 4:34 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] Using new SVN for PostGIS

Greg Boone wrote:
> I am not sure I understand. Please correct me if I am wrong here. Are
> you preparing to create your own SVN repository outside fdordbms?
> If so, that is not the expected solution.

Definitely, I'm not going to go with my own repo.

> We expect you to merge your changes into the trunk of fdordbms and
> have PostGIS be an equal to the ODBC and MySQL providers with a build
> process that builds all three.

Yes, this is exactly how I'd like to merge too.

> Therefore, you would have to integrate any changes you
> made to fdocore or fdodbms in order to support the PostGIS provider
> back into the respective branches of these repositories.

That's right.


I'll try to ask this way:

I've been disconnected from the SVN changes in fdocore/trunk and
fdordbms/trunk for a ~1 month.

If I update my working copies and continue building PostGIS FDO
against current fdocore/trunk, and finally merge with fdocore/trunk and
fdordbms/trunk, which version of Autodesk Map 3D and MapGuide
can I target with my PostGIS FDO?

This question is important because as far as I know, fdocore has been
frozen at some point, for nearest release.

Will it be possible to use the PostGIS FDO with Map 3D Hammerhead ?


Cheers
-- 
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals

-------------- next part --------------
An embedded message was scrubbed...
From: "Brent Robinson" <brent.robinson at autodesk.com>
Subject: [fdo-dev] Binary compatibility change to fdo.dll (trunk version)
Date: Fri, 15 Dec 2006 16:05:02 -0500
Size: 2143
Url: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20070116/2f2df996/attachment.mht