[fdo-internals] Hosting FDO 3.5 builds / Binaries for CentOS
and Ubuntu
Trevor Wekel
trevor_wekel at otxsystems.com
Wed Feb 17 19:29:03 EST 2010
Hi Helio,
I have been working on Ubuntu packaging for the 32 bit build and have just had a chance to look at your fdo.spec and patch file. I have a few questions:
Does Linux have a /usr/lib64 in addition to a /lib64?
Are you still building to /usr/local? From my Ubuntu work, installing packages to /usr/local seems to be a bit of a no-no. The Ubuntu lintian tool generate a whole whack of errors when I try to target /usr/local.
Do we want to break each provider out into a separate install package (rpm on Fedora/CentOS, deb on Ubuntu/Debian)?
Also, the RegistryUtility patch seems reasonable to me.
Thanks,
Trevor
-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Helio Chissini de Castro
Sent: February 13, 2010 10:16 AM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] Hosting FDO 3.5 builds / Binaries for CentOS and Ubuntu
Hello all
I just did today RPM for FDO trunk, in Fedora 12, using the CMake Build.
I called 3.5.0 anyway, with 0.1 as rpm release. Done for both 32 bits and 64 bits. Is suitable for Mandriva too with a little tweaks.
Attached is the spec and a patch to approve commit in lib64.
I tried to made it as simple as possible.
[]'s
On Friday 05 February 2010 16:52:46 Trevor Wekel wrote:
> Hi Greg,
>
> Yes the RPM and .spec files would certainly help for the CentOS builds.
> The file list in the .spec file should also help with building the
> .deb packages.
>
> Thanks Greg,
> Trevor
>
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> Sent: February 5, 2010 11:27 AM
> To: FDO Internals Mail List
> Subject: RE: [fdo-internals] Hosting FDO 3.5 builds / Binaries for
> CentOS and Ubuntu
>
> I am not sure about building 32bit binaries on a 64bit OS. Never tried
> that. I know it works the other direction.
>
> So, I have access to RPM and .spec files for FDO. Is this what you
> need? I guess you need a script to run these as well.
>
> Greg
>
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Trevor
> Wekel
> Sent: Friday, February 05, 2010 12:53 PM
> To: FDO Internals Mail List
> Subject: RE: [fdo-internals] Hosting FDO 3.5 builds / Binaries for
> CentOS and Ubuntu
>
> Hi Greg,
>
> Starting with Windows is good but I will be working on both Windows
> and Linux in fairly short order. I am targeting FDO 3.5 but all of
> the linux rpm/deb submissions would have to be ported to trunk as well.
>
> Do you think we be able to run both the 32 and 64 bit Windows builds
> on a single Windows Web Server 2008 x64 VM? If so, I will get some of
> the licensing resolved and set up the build machines. The list of
> third party components/packages will certainly help once the build
> machines are set up.
>
> Thanks,
> Trevor
>
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> Sent: February 5, 2010 10:01 AM
> To: FDO Internals Mail List
> Subject: RE: [fdo-internals] Hosting FDO 3.5 builds / Binaries for
> CentOS and Ubuntu
>
> This sounds great.
>
> Maybe we can start with Windows to get going and then move onto the
> Linux distributions?
>
> Which build of FDO are you targeting? 3.5.0 or trunk or both?
>
> How would you like to proceed? Do you need a list of Thirdparty
> components\packages you will need to have installed in order to run
> the build?
>
> Greg
>
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Trevor
> Wekel
> Sent: Friday, February 05, 2010 11:52 AM
> To: FDO Internals Mail List
> Subject: RE: [fdo-internals] Hosting FDO 3.5 builds / Binaries for
> CentOS and Ubuntu
>
> Hi Greg,
>
> Yes. I was planning to publish all the FDO builds required for MapGuide.
> This would include 32 and 64 bit binaries for Windows and Linux. The
> build machines would be accessible via remote desktop and ssh. We
> already have a small group of build/install maintainers for MapGuide
> and I would be happy to add anyone who wants to help out with FDO.
>
> I am in the process of getting the software licensing figured out for
> the builds and will be creating new virtual machines over the next
> couple of weeks. All of the machines will be hosted on a private
> subnet and exposed through a virtual IP address. Since there will be
> quite a few VMs to orchestrate, I will also be looking into BuildBot
> and setting up a local Subversion proxy to reduce the load on OSGeo.
>
> Thanks,
> Trevor
>
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> Sent: February 5, 2010 9:24 AM
> To: FDO Internals Mail List
> Subject: RE: [fdo-internals] Hosting FDO 3.5 builds / Binaries for
> CentOS and Ubuntu
>
> Hi Trevor,
>
> I think I can speak for the PSC and state that this would be a great idea.
> Are you looking to publish both Windows and Linux builds?
>
> Greg
>
>
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Trevor
> Wekel
> Sent: Friday, February 05, 2010 6:36 AM
> To: FDO Internals Mail List
> Subject: [fdo-internals] Hosting FDO 3.5 builds / Binaries for CentOS
> and Ubuntu
>
> Hi list,
>
> I am a member of the MapGuide Open Source PSC and responsible for the
> build infrastructure for MGOS. We are currently looking at revamping
> the build infrastructure for the MapGuide 2.2 release. Since MapGuide
> depends closely on FDO, we may be able to make better use of the build
> VMs by using them to build FDO as well.
>
> Since I am already hosting the MapGuide builds, hosting the FDO builds
> on the same VMs would not cost me (or the FDO project) anything.
> Regular FDO builds (nightly/weekly) can be accommodated. Builds
> intended for general community use would have to be posted to the
> OSGeo download site since I do not have unlimited bandwidth.
>
> Moving the FDO builds to community managed infrastructure may provide
> faster turnaround on FDO releases and get the FDO community more
> involved in the project.
>
> In addition to the builds, I was unable to find any build scripts in
> the FDO repository for creating CentOS rpms or Ubuntu debs. I am
> currently investigating binary packaging for FDO and will be able to
> contribute deb and rpm creation scripts to the project if they do not already exist.
>
> Does this sound like an endeavour that the FDO PSC would like to pursue?
>
> Regards,
> Trevor
--
Helio Chissini de Castro
South America and Brazil Primary Contact KDE Developer since 2002
More information about the fdo-internals
mailing list