[fdo-internals] RE: GCC 4.4 and Oem upgrade

[Traian Stanev]

I think we should also consider doing the same for the FDO builds.

I am copying this thread to fdo-internals to poll people's opinions.


Traian


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Tom Fukushima
Sent: Monday, May 10, 2010 11:54 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RE: GCC 4.4 and Oem upgrade

Thanks. I think that we should go with #2.

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: Monday, May 10, 2010 9:20 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RE: GCC 4.4 and Oem upgrade

Hi Tom,

Different versions of Berkeley DB may require repository upgrades.  With all of the different distro versions floating around, it will be more difficult to determine when a repository upgrade is required.  MGOS 2.2 compiled on CentOS 5 and MGOS 2.2 compiled on Ubuntu 9.10 will likely not have compatible repositories.

Regards,
Trevor


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Tom Fukushima
Sent: May 10, 2010 9:16 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RE: GCC 4.4 and Oem upgrade

I don't understand "Repository migration more difficult".  Please explain what you mean by repository migration and why it is more difficult.

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: Monday, May 10, 2010 5:23 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] GCC 4.4 and Oem upgrade

Hi everyone,

Rohit and I have started chatting about the GCC 4.4 upgrade http://trac.osgeo.org/mapguide/wiki/MapGuideRfc92.  From previous work, I know that we need to update some of our third party dependencies.  We have a couple of options for Linux:

1. Update the necessary Oem components in the vault
Advantages:
- No change to build system
- Consistent components for Linux and Windows
- We can patch Oem whenever we want

Disadvantages:
- Security patches are never up to date
- More code to maintain in our vault

2. Go native and use the distro libraries on Linux  
Advantages:
- Security patches always up to date
- Faster build downloads
- Easier Linux packaging
- It will force us to post our fixes back to the original projects and be a better open source citizen

Disadvantages:
- Components may not consistent between Windows/Linux or even different Linux distros
- Repository migration more difficult


Any preferences/thoughts?


Regards,
Trevor & Rohit

_______________________________________________
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