+1 Also, depending on how one keeps releases in the SVN, the Build Instructions can copy-on-write and only need to be changed on the trunk when there is a change in what is happening on the trunk. All previous versions will still have theirs.
They can also be in HTML, or there could also be an HTML version in the repo. This also puts the Build instructions in the ideal place for their QA, their being used to make a build of the current code, etc. Did I say I like it? +1 - Dennis -----Original Message----- From: Rob Weir [mailto:[email protected]] Sent: Tuesday, September 20, 2011 11:41 To: [email protected] Subject: Re: automake insteed configure On Mon, Sep 19, 2011 at 6:00 AM, Raphael Bircher <[email protected]> wrote: > Hi all > > In the past, configure was only rebuild if needed by samone (releng?) in > Hamburg. Now Mathias Bauer recommends to build configure.sh everytime and > make automake to the default step by the buildprocess. I think this Step > should be don ASAP. > I think that's not a load of changes, but I have a question: "How to run > automake, and where it is located" can sameone help me. > So we're diverging now from what is in the Building Guide. How do we want to keep these in sync, so new developers have accurate instructions for how to build? I know we have information on the wiki. But that gets out of synch very quickly. And if, in 6 months from now, someone needs to go back and build AOOo 3.4.0 again, the instructions on the wiki will now be different, and not good for the older build. So how do we keep build instructions that are accurate and tied to a revision of the project? Wouldn't storing build instructions in SVN, in the source tree, help here? Then when a programmer changes the build, they don't need to leave their editor or IDE. They just update the build instructions and commit it. -Rob > Thanks a load > > Greetings > Raphael > -- > My private Homepage: http://www.raphaelbircher.ch/ >
