gmane.comp.gnome.ximian.openoffice

[ANN] ooo-build has been folded into LibreOffice

Thorsten Behrens — 2011-02-09T08:10:51

Dear fellow ooo-build hackers,

as announced last year, the ooo-build project has joined forces with
LibreOffice. With the successful LibreOffice 3.3 release, we'll now 
formally discontinue this project.

Effective today, this mailing list will be switched off - please use
the libreoffice< at >lists.freedesktop.org list instead, for everything
development-related.

See http://www.libreoffice.org/get-involved/developers/ for more
information on LibreOffice development.

Rest in peace go-oo, and long live LibreOffice! :)

Best regards, and many thanks for your past and future
contributions,

IllegalArgumentException in Java-Extension only in Go-oo

Dietmar — 2011-02-06T10:22:24

First my apologize to address this topic to this list, because it is
probably a bit off-topic, nevertheless, I'd appreciate if a developer
could quickly feedback.

I wrote an extension for OOo in Java which works fine in native OOo.
Recently I switched to Debian Squeeze and am using the packaged OOo
3.2.1 which afaik is based on Go-oo.
Here, this extension throws an exception



Now my question:
Are you aware a some features of the api that were disabled in Go-OO, which might cause this effect?
Or some more stringent compiler options (i.e. a mistake in my programming that is tolerated in native OOo but not in Go-oo?)

The same occurs on Ubuntu 10.10 with Libreoffice 3.3.
I also checked with Sun-Java 6 in Debian, same result as with OpenJDK 6.

Thanks for your support
   Dietmar

Problem while building openoffice go from sources.

Morgoth Evil — 2011-01-05T09:09:38


Hi.
I get this error while building new version of openoffice.
I completely lost and can't solve this problem.

=============
Building module cli_ure

Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/inc

Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/source

Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/version

Entering
/root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/source/basetypes

Entering
/root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/source/climaker
Making:    all_climaker.dpslo

Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/unotypes
MONO_PATH=../unxlngi6.pro/bin:
LD_LIBRARY_PATH=/root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/solver/320/unxlngi6.pro/lib:../unxlngi6.pro/lib
../unxlngi6.pro/bin/climaker  \
         --out ../unxlngi6.pro/bin/cli_uretypes.dll \
         --keyfile ../unxlngi6.pro/bin/cliuno.snk \
         --assembly-version 1.0.4.0 \

[ANN] ooo-build is going to be folded into LibreOffice

Thorsten Behrens — 2010-10-25T13:50:47

Dear fellow ooo-build hackers,

no news to many of you, just to give a formal heads-up: we're in the
process of joining forces with LibreOffice, and are currently
merging most of the patches there. So going forward, this list and
the go-oo.org website really don't make much sense anymore.

Please move over to libreoffice< at >lists.freedesktop.org for technical
discussions, or join us at #libreoffice on irc.freenode.net

Cheers,

libreoffice 3.2.99.1 mono compile error

Gökçen Eraslan — 2010-10-02T15:12:50

Slovak Translations of go-oo

Branislav Klocok — 2010-10-01T15:59:27

Dear go-oo developeres,

My name is Branislav Klocok and I am the leader of Slovak localization 
team of OOo. It was brought to my attention by one of the Slovak users 
of go-oo that the Slovak translation are not 100% up to date and I 
would like to ask you what is the process here in go-oo concerning 
translations? Do you take translations only from the OOo (which 
sometimes in not updated for Slovak since we are using a different 
build system) or you are having a another process?

Best regards,

Do you consider Go-oo project to be a fork ofOpenOffice.org?

espinosa_cz — 2010-09-30T00:39:19

Dear Go-oo developers,
Do you consider Go-oo project, your project, to be a fork of OpenOffice.org?

General public opinion seems to be quite sure and general perception is 
that it is a fork or at least branch; considering Go-oo as fork is 
matter of habit for most forum speakers.

My stance same is – Go-oo is a patchset, with a lively community, 
providing own build, forums, but still it is primarily a patchset. I 
would consider a bed news for whole open-source community if such 
important project would fork.

Wikipedia is inconsistent here. This does not help.

In OpenOffice.org Wikipedia entry 
(http://en.wikipedia.org/wiki/OpenOffice.org) is clearly stated that 
Go-oo is fork (details below).

In Go-oo Wikipedia entry (http://en.wikipedia.org/wiki/Go-oo) is however:
Go-oo .. is a concentrated set of patches for the cross-platform 
OpenOffice.org office suite.

Details from OpenOffice.org Wikipedia entry 
(http://en.wikipedia.org/wiki/OpenOffice.org):
[citation]
Although branded as OpenOffice.org, the

Patch for building against libxml2 version 2.7.4 and2.7.5

Jonas Finnemann Jensen — 2010-09-27T19:47:17

Opengrok for Go-oo

Cédric Bosdonnat — 2010-09-27T09:29:11

Hi folks,

I installed and setup opengrok to run on go-oo.org on Friday. You can
reach it at the following URL:

http://opengrok.go-oo.org

Please note that this is still experimental and may require some config
changes. Don't hesitate to report the annoying stuffs you encounter when
using it. If you need to have repos like l10n, libs-extern or
libs-extern-sys indexed, please ask!

I hope this will be useful for you!

--
Cedric

Failed to compile go-oo

Nadav Vinik — 2010-09-25T05:52:43

New translations commited in the old stale GNOME repoof ooo-build

Lucian Adrian Grijincu — 2010-09-24T00:08:59

There have been some commits to the GNOME repo
http://git.gnome.org/browse/ooo-build/ that have updated some
translations.

I'm pretty sure they have missed the THIS_REPO_IS_DEAD warning and
just commited and went away. I don't know if you're tracking any
activity from that repo; if not, I think setting up some triggers
(e.g. an automatic email every time something in po/ gets changed)
would help.

Add Romanian translation

Lucian Adrian Grijincu — 2010-09-24T00:04:52

Please CC me if you need any further info.

icu4c 4.2.1 problem in master

Miklos Vajna — 2010-09-23T22:59:32

smoke test does not work in master

Petr Mladek — 2010-09-21T08:01:03

Hi Noel,

Rene told me that smoke test does not work in master. It ends with

--- cut ---
officeconnection.cxx:138:Assertion
Test name: (anonymous namespace)::Test::test
setUp() failed
--- cut ---

It is started when you just run build in smoktestoo_native.

Could you please have a look?


Best Regards,
Petr

officecfg module tries to write outside of builddirectory

Gökçen Eraslan — 2010-09-19T13:52:48

[PATCH] fixed the sed command to extractcompletelangiso correctly

Andras Timar — 2010-09-18T20:52:19

Hello,

I tried to build from the current ooo-build snaphot and I encountered
an error. The sed command that is defined in bin/setup.in did not
generate the expected result. I don't know why I have not triggered
this error before.

The currend sed commad has the following result:
completelangiso="af
This is wrong, eval dies on it (quote mismatch). The attached patch
solved the problem. May I push it?

Best regards,
Andras

ANNOUNCE: ooo-build-3.2.98.1 released (3.3-alpha1)

Petr Mladek — 2010-09-16T15:17:12

Hi,

I am happy to announce 3.3-alpha1 release of ooo-build master. You 
might find it at

http://download.go-oo.org/3.3/ooo-build-3.2.98.1.tar.gz
http://download.go-oo.org/3.3/ooo-build-3.2.98.1.tar.gz.md5

It took very long time because of many changes, vacations, ...
   

New source tarballs:
-------------------- 

As announced in other mails, we started to move patches from ooo-build
to the OOo git sources. It means that the plain OOo source tarballs are
not longer usable. Instead, ooo-build-<version>-<piece>.tar.bz2 are
needed. They are automatically downloaded by the script ./download.

Alternatively, you might get them at http://download.go-oo.org/3.3/ We
started to provide the prebuilt tarballs again because people had
troubles with CGIT...

The tarballs has the structure:

+ ooo-build-<version>-<piece>
+ module1
+ prj
+ source
+ module2
+prj


This structure is typical for software sources. It will be nice for the
split build. We really need got forward and get split build into life.

new ooo-build workflow for developers and packagerts

Petr Mladek — 2010-09-10T18:52:43

Hi,

there is still confusion how to use ooo-build after we started to move
the diffs to git.

It is clear that developers and packagers has a bit different needs. I
tried to describe the current suggested workflow at 
http://www.freedesktop.org/wiki/Software/ooo-build/BuildingIt#Buildingfordifferentpurposes


There are currently two FIXME's:

1. I think that --with-git=/path-to-another-clone-dir should cause
   that the other clone is used as reference to create the new clone;
   the new clone still should push directly to freedesktop.

   Is this true? Kendy, Thorsten?

2. I think that --with-tag option does not longer make sense. If you
   want to use another ooo sources, you should use the new
   --with-source-version option that is more descriptive

   I am going to remove the --with-tag option


Feel free to suggest a better workflow. Point out problems with the
current one, ... Add more tips, e.g. the Fridrich's --with-src dir, ...

BTW: I think that we can't longer support build of pure OOo sources.

--with-srcdir build

Fridrich Strba — 2010-09-07T07:50:54

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello, good people,

I would like to explain once again what mean the variable SRCDIR. If one
passes the --with-srcdir option, the SRCDIR will be set to a dedicated
directory where ./download will download tarballs and other files that
are used for build. This is useful if you have several builds coexisting
on the same machine. Because it is saving quite a considerable amount of
space since a lot of the tarballs will be having only one instance on
the disk.

Now, if you don't pass the --with-srcdir option, the SRCDIR will be set
to the subdirectory "src" in ooo-build sources. But this is a
coincidence. If you want to refer to that directory as such, you should
use TOOLSDIR/src. TOOLSDIR/src contains files that are part of ooo-build
tarball and not downloaded during the build process.

Please, keep this in mind because once the SRCDIR and TOOLSDIR/src get
messed up, it is pretty complicated to unwind.

Cheers

Fridrich
-----BEGIN PGP SIGNATURE-----
Version: GnuPG

[PATCH] bin/g: don't use git status

Miklos Vajna — 2010-09-06T20:28:48

support to tag more repositories

Petr Mladek — 2010-08-31T13:20:05

Hi Kendy,

I had to improve the "g" script to be able to tag the git repositories
and push the tags. Please, find the diff attached.

The changes are:

+ add quotes around the message string for commit command;
          I wonder how it worked

+ git tag does not support --message=<msg>, so I had to pass
          -m <msg> as a single paramete; I think that we could actually
          use the same hack for "commit" as well

+ the extra parameter for "tag" is not file path

+ the new tag is not detected by "status", so I need to force
          the "push"


Any comments before I commit it ;-)


Best Regards,
Petr