Oh, I see ...
The branching is somewhat weird in OpenOffice.
Yes, then you can do the work in trunk. Try to use "svn merge" to bring
the changes from the gbuild branch.
Unfortunately I moved configure.in to configure.ac so those changes will
have to be done by hand, but it's probably not the only case.
Pedro.
On 09/24/15 02:08, Damjan Jovanovic wrote:
Hi
We aren't branching trunk to release 4.1.2, we are porting specific
patches from trunk to the pre-existing AOO410 branch and then tagging
that as the release. The state of trunk doesn't affect the release
stability.
Damjan
On Wed, Sep 23, 2015 at 10:06 PM, Pedro Giffuni <p...@apache.org> wrote:
Hi again Damjan;
I was assuming that we are sort of preparing for a release and we don’t want
ugly surprises with the build system. On second thoughts we do have a bunch
of buildbots so we will detect any wrong-going within the build system.
Well, no one is currently using the build branch so I would suggest giving it a
try. If you find it too much trouble then you could do the work on trunk. In
either
case the idea is to preserve the Oracle changes by using “svn merge”.
I think it’s a fair amount of work but so far you have proved being very capable
with such changes :).
Thanks +1
Pedro.
Il giorno 23/set/2015, alle ore 10:48, Pedro Giffuni <p...@apache.org> ha
scritto:
Hi Damjan and list;
Working on gbuild would certainly be welcome, however please do so on the
gbuild branch.
The branch is really old, I recall it was broken for FreeBSD, so it needs
updating. I realize the request may seem inconvenient but the gbuild branch
contains the last OpenOffice.org code related to gbuild and was relicensed by
Oracle for our use.
Pedro.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
