Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8CC9CE8A0 for ; Thu, 31 Jan 2013 15:28:20 +0000 (UTC) Received: (qmail 38026 invoked by uid 500); 31 Jan 2013 15:28:18 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 37924 invoked by uid 500); 31 Jan 2013 15:28:18 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 37906 invoked by uid 99); 31 Jan 2013 15:28:18 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 15:28:18 +0000 Received: from localhost (HELO [9.155.131.51]) (127.0.0.1) (smtp-auth username hdu, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 15:28:17 +0000 Message-ID: <510A8DBE.6050804@apache.org> Date: Thu, 31 Jan 2013 16:29:02 +0100 From: =?ISO-8859-1?Q?Herbert_D=FCrr?= User-Agent: generic MIME-Version: 1.0 To: dev@openoffice.apache.org CC: hdu_ooo@alice.de Subject: Re: Ubuntu Build Instructions References: <51094AEC.3010709@gmail.com> <510A67C9.6010503@apache.org> <510A768A.1030500@apache.org> <510A7805.7000805@googlemail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 31.01.2013 15:55, janI wrote: > but it still highlight the problem I had in the beginning...our wiki has > really much valuable information, but to an extent it is shadowed by > identical information which are not maintained. > > I searched for ubuntu build instruction way back, and as you can imagine > got confused. Thx. to the brilliant help from this list I got it up and > running. > > I hope we in the short future can get our wiki a bit streamlined (I am not > thinking about removing information, but simply mark it as outdated, with a > link to the newer information. I totally agree and try to do it whenever I stumble over something like this. I'd also suggest to reuse pages even if they contain obsoleted content. If their title is general purpose, is linked to from many other places and easily findable then updating them is a better solution IMHO. If anyone needs to access their older outdated content it is good to know that it is still available via Wiki's wonderful page history feature. > @herbert regarding buildbot, I can see your point and agree with it. > However I still think we should document exactly how our binary > distributables are made. I have actually not been able to produce an exact > match yet where I have tried. When people want to play with the system it > is nice to have a stable start like rebuilding the release and the same > result. For the exact configuration switches please see the page [1] I linked to in my previous mail. To create an exact match on Linux you'd have to install the "oldest common denominator" system that is used to build releases. We can ask Ariel to provide all the glorious details of this system, AFAIK they are plain RHEL5 and RHEL6, right? These old systems are great for building maximum-compatibility releases, but IMHO they are not much fun For developing. I personally love having up-to-date versions of gdb, valgrind, perf-tools, git-svn, btrfs snapshots, KVM/virtualbox, python, etc. but maybe that's just my personal disposition. [1] https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-buildflags I'm looking forward to see and talk to you on FOSDEM this weekend! Herbert