[mapguide-internals] Mapguide -> FDO dependencies?

[Tom Fukushima]

I like this.  Automating it will keep it from getting out of date in case it is updated in one place but not the other.  Maybe we should use a svn:externals tag for this like we do for CsMap and Fusion. Other than the increased download, does anyone see a problem with adding a svn:externals property for the MgDev/Oem/FDO directory?

Actually, if we use the svn:externals tag, then the original problem goes away because there is no need to figure out which version of FDO to get anymore.


 
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of UV
Sent: Sunday, April 05, 2009 11:26 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Mapguide -> FDO dependencies?

Hi Tom,

Once the release notes are written we can find the info it in there. 
However, I suggest to use the word dependency as its quite descriptive 
for the search.

For the ongoing work I think the best place is a file in the SVN which 
is shown on the road map under a new paragraph called FDO dependency.

As the dependency is a moving target (FDO being branched into 3.4 soon) 
we should think a moment how to do that cleverly so the information]
is updated when that branch is made.
The creation of the release branch looks exactly like the important 
event that should not be missed in the roadmap of the internals website.

I am not very familiar with the project website infrastructure so maybe 
its too much to teach TRAC to extract files from SVN
but I think this would be the best way to do it.

Generally, it seems very beneficial if the project website simply 
presents views not only on trac and but also on SVN.
The more information we can extract from SVN the more up to date 
information we will have on the project website.....
this should eventually include the build server page also.

What do you think?


Tom Fukushima wrote:
> Hi UV,
>
> Since you have built things most recently from trunk and followed whatever instructions we have on the trac site, you may be best qualified to tell us which page you would have expected the information on.  Did you find any page where it would have been best to have that information?
>  
> BTW, assuming that MGOS trunk builds against FDO trunk should be good.
>
> Thanks
> Tom 
>
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of UV
> Sent: Saturday, April 04, 2009 5:40 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] Mapguide -> FDO dependencies?
>
> I am not sure if there are dependencies from mapguide to FDO that the 
> fdo people would know about it.
> I would think if its the mapguide code using FDO libs the mapguide 
> project should be clear about the dependencies.
> Which are they and where to find them please?
> This is essential configuration management and it should be clear for 
> everyone for things to work.
>
> So if I am building the trunk should I be building against fdo trunk? 
> That was my assumption.
> Is this really not written down anywhere?
> Especially if suddenly new library versions show up and there is no way 
> to check what this is about except this list.
> Please!!!
>
> Jason Birch wrote:
>   
>> The best place to ask about this is fdo-internals mailing list (copied; UV, you'll need to subscribe to reply).
>>
>> I'm surprised that it outputs a gdal14.dll.  Was that using a Debug or Release target?  I've been using the FDO release candidate SDKs for the installer builds, so wouldn't have noticed this.
>>
>> I think that MapGuide trunk (at least prior to our 2.1 branch) should probably be building against the fdo 3.4 branch.
>>
>> Jason
>>
>> -----Original Message-----
>> From: UV
>> Sent: March-31-09 10:22 PM
>> To: MapGuide Internals Mail List
>> Subject: [mapguide-internals] FDO dependencies?
>>
>> The latest FDO trunk builds a gdal14.dll
>>
>> however, gdal16.dll seems to be the version used for FDO 3.4.0
>>
>> whats the story please?
>> is there a place to find out about such things?
>> If not we need one!
>>
>> cheers,
>> UV
>> _______________________________________________
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
>>   
>>     
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>   

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