[arch-dev-public] go-openoffice to testing/extra
I'd like to bring the Novell "fork" of OpenOffice.org to testing and later to extra. But it's not (yet) a real fork. More a major improvement in features and lower packager maintenance. It also allows installation into /usr instead of /opt. Beside Novell/SuSE also Gentoo, Frugalware, ArkLinux and Debian use it as their main office suite. It has some additional features (svg support, multimedia for presentations, faster startup and kde(3) integration, hopefully later easy splitted packages). But main reason is faster integration of fixes and features. Not one additional patch is required to build it :) See http://go-oo.org/discover/ for more. I'm still unsure if it will become an additional flavor of OOo in our repos or if I will make it later a complete replacement of the Vanilla Sun OpenOffice for ArchLinux. It also gives our devs and community members an easier way to contribute to go-oo, e.g. you can help porting for KDE4 integration that is still in (so they told me) unusable state. Any objections adding go-openoffice? -Andy (technical note: build requirements are even higher than for vanilla OOo, 13gb space proved to be no more enough space to build this monster... - have fun with 'abs')
Andreas Radke schrieb:
I'd like to bring the Novell "fork" of OpenOffice.org to testing and later to extra. But it's not (yet) a real fork. More a major improvement in features and lower packager maintenance. It also allows installation into /usr instead of /opt. Beside Novell/SuSE also Gentoo, Frugalware, ArkLinux and Debian use it as their main office suite.
I use OOo rarely, so I trust your judgement there. As soon as it works as well as it does now, do it.
On Thu, Apr 16, 2009 at 3:43 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Andreas Radke schrieb:
I'd like to bring the Novell "fork" of OpenOffice.org to testing and later to extra. But it's not (yet) a real fork. More a major improvement in features and lower packager maintenance. It also allows installation into /usr instead of /opt. Beside Novell/SuSE also Gentoo, Frugalware, ArkLinux and Debian use it as their main office suite.
I use OOo rarely, so I trust your judgement there. As soon as it works as well as it does now, do it.
Yeah, for the record, I used google docs when I need to view these things, but always have OOo installed. Like Thomas, I say that whatever you think is best is fine by me
2009/4/16, Andreas Radke <a.radke@arcor.de>:
Any objections adding go-openoffice?
Go for it. -- Arch Linux Developer (voidnull) AUR & Pacman Italian Translations Microdia Developer http://www.archlinux.it
On Thursday 16 April 2009 04:21:40 pm Andreas Radke wrote:
Any objections adding go-openoffice?
-Andy
I think, go-oo should replace ooo vanilla in the near future, all major distributions are doing so, but that is not the sole reason, it has better integration, more fixes, more functionality, less patches to apply and will help the end-user at the end.
Em Sábado 18 Abril 2009, às 11:37:51, Eduardo Romero escreveu:
On Thursday 16 April 2009 04:21:40 pm Andreas Radke wrote:
Any objections adding go-openoffice?
-Andy
I think, go-oo should replace ooo vanilla in the near future, all major distributions are doing so, but that is not the sole reason, it has better integration, more fixes, more functionality, less patches to apply and will help the end-user at the end.
+1000 for that
On Saturday 18 April 2009 10:41:07 am Douglas Soares de Andrade wrote:
Em Sábado 18 Abril 2009, às 11:37:51, Eduardo Romero escreveu:
On Thursday 16 April 2009 04:21:40 pm Andreas Radke wrote:
Any objections adding go-openoffice?
-Andy
I think, go-oo should replace ooo vanilla in the near future, all major distributions are doing so, but that is not the sole reason, it has better integration, more fixes, more functionality, less patches to apply and will help the end-user at the end.
+1000 for that I have to disagree with myself this time, I have installed the go- openoffice in testing, and it offers less functionality a than vanilla openoffice. I can't create tables, opening documents with tables reveal no tables at all, and worst of all, I can;t open openxml documents, which is the key feature of go-oo.
Can anyone confirm this? It is hurting me a lot, since I rely heavily on an office suite for work. -- Thanks, Eduardo "kensai" Romero
Tables are working fine here. Any specific one that you are trying? I did not tried to open a openxml document. All the rest works fine too. -- Hugo
On Wednesday 29 April 2009 10:53:24 am Hugo Doria wrote:
Tables are working fine here. Any specific one that you are trying?
I did not tried to open a openxml document. All the rest works fine too.
-- Hugo Well, I have found this is random, cause now I can open them perfectly, heh. I think this is some random bug in the release candidate. -- Thanks,
Eduardo "kensai" Romero
pkg moved to extra. Any idea how to handle the langpacks until we get splitted packages? 1) use symlinks from the vanilla langpacks to the go-oo location. needs updates on the langpacks for every go-oo update what may annoy people using only the vanilla OOo. 2) separate langpack packages, probably 1:1 set to the vanilla ones. 3) no langpacks at all. leave it up to AUR community. opinions? -Andy
Andreas Radke wrote:
pkg moved to extra.
Any idea how to handle the langpacks until we get splitted packages?
1) use symlinks from the vanilla langpacks to the go-oo location. needs updates on the langpacks for every go-oo update what may annoy people using only the vanilla OOo.
I assume this is because of the go-oo directory in /usr/lib has the pkgver in it. Can you not just do a sed or two so that is /usr/lib/go-openoffice? Or if I am way off, can you explain the problem in more detail. Allan
Am Sat, 02 May 2009 00:09:01 +1000 schrieb Allan McRae <allan@archlinux.org>:
Andreas Radke wrote:
pkg moved to extra.
Any idea how to handle the langpacks until we get splitted packages?
1) use symlinks from the vanilla langpacks to the go-oo location. needs updates on the langpacks for every go-oo update what may annoy people using only the vanilla OOo.
I assume this is because of the go-oo directory in /usr/lib has the pkgver in it. Can you not just do a sed or two so that is /usr/lib/go-openoffice?
Or if I am way off, can you explain the problem in more detail.
Allan
This is wanted. It allows you to install several versions along each other. Like we do now in openoffice-base{,beta,devel). It would be a mess to sed this out. It's a wanted upstream feature and one of the go-oo improvements. -Andy
Andreas Radke wrote:
Am Sat, 02 May 2009 00:09:01 +1000 schrieb Allan McRae <allan@archlinux.org>:
Andreas Radke wrote:
pkg moved to extra.
Any idea how to handle the langpacks until we get splitted packages?
1) use symlinks from the vanilla langpacks to the go-oo location. needs updates on the langpacks for every go-oo update what may annoy people using only the vanilla OOo.
I assume this is because of the go-oo directory in /usr/lib has the pkgver in it. Can you not just do a sed or two so that is /usr/lib/go-openoffice?
Or if I am way off, can you explain the problem in more detail.
This is wanted. It allows you to install several versions along each other. Like we do now in openoffice-base{,beta,devel). It would be a mess to sed this out. It's a wanted upstream feature and one of the go-oo improvements.
OK, but as far as I can tell, the langpacks only work with openoffice-base and not openoffice-base-{beta,devel}. If that is correct, what is wrong with installing go-oo to /usr/lib/go-openoffice and having langpacks work with that and any other versions go to /usr/lib/go-openoffice-$ver? Allan
participants (8)
-
Aaron Griffin
-
Allan McRae
-
Andreas Radke
-
Douglas Soares de Andrade
-
Eduardo Romero
-
Giovanni Scafora
-
Hugo Doria
-
Thomas Bächler