openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Rist <>
Subject Re: [BUILD] EPM for building packages - was [BUG] AOO cannot be installed
Date Wed, 04 Jan 2012 22:09:24 GMT

On 1/4/2012 11:44 AM, Andrew Rist wrote:
> I am trying to create the buildbots so that there is now magical 
> secret sauce to keep them working.
> Thus, I am trying to create a 'recipe' for creating the build machine 
> which includes:
>  * vanilla version of an OS (Ubuntu 10.04 as a starting point for
>    buildbots so far)
>  * a set of dependencies (which I am currently creating as a set of
>    apt-get commands for the machine)
>  * a script for running the build (which is translated into the
>    buildbot config file)
> I practice these on my machine and once they are stable and 
> repeatable, then they are ready for deploy as a buildbot.
> I am wary of steps that include building and deploying patched 
> software outside of this process.
> EPM is currently in this category.  What is our best solution for EPM?
> 1. find a dependency that can be repeatably loaded in the dependencies
>    list
> 2. create a configure option of --with-EPM-path=<URL> and download and
>    build a patched EPM during the build
like the existing option of --with-epm-url, for instance....
seriously, I got it now, and I'm implementing this into buildbot.
I think this needs to be added into the ./configure --help

> I know I have not included the option of prebuilding the patched EPM - 
> this is intentional, as this leads to highly customized and 
> non-reproducable build machines, so I think that is a bad course to 
> follow.
> thoughts??
> A.
> On 1/2/2012 12:01 PM, Ariel Constenla-Haile wrote:
>> On Mon, Jan 02, 2012 at 07:41:35PM +0100, Raphael Bircher wrote:
>>> Hi Dave
>>> Just to clarify. Mechtilde is a contributor since day 0 - 7 years.
>>> She is one of the moast experienced QA here, and a verry skilled
>>> manual tester. So she is not a newbe at all.
>>> I build only for mac, for linux i point to the Buildbot too. If this
>>> builds don't work for a Linux distribution it is a serios problem,
>>> so it's right to bring it on the list.
>>> What Mechtilde miss, are de frequently snapshots from the project it
>>> self, not from same contributors. The test build should be from the
>>> same mashine as the final release. You can build AOO on two
>>> computers with Linux, you will have two different builds even you
>>> use the same revision.
>>> For this reason, test builds has to come from the same mashin as the
>>> release. For my point of view it's not a good idea to use a
>>> contributors computer for it. So the main plattform Wendows, Linux,
>>> Mac realy need a Buildbot, and this is not a "nice to have" it's a
>>> *realy urgent task*
>>> And if one of this Buildbot produce unusable builds, then we have a
>>> serios problem.
>> Those build are unusable due to the EPM version, a subject that has been
>> discussed since the epm removal, so I have no idea why the buildboot
>> ended with a system epm.
>> IMO the Linux build boot should produce also RPM packages, not only
>> DEBs. And nightly builds are useful for keeping the code base buildable,
>> but for testing purposes it would be more useful a weekly developer
>> snapshot.
>> Regards


Andrew Rist | Interoperability Architect
OracleCorporate Architecture Group
Redwood Shores, CA | 650.506.9847

View raw message