OpenOffice in parts
Message
OpenOffice in parts
I need to install OpenOffice in parts (I need only Writer and Calc). I know that there is such a possibility with customized build from go-oo.org in Windows (you are allowed to choose which parts of OO to install). Is there such a possibility in Gentoo?
Nope, there are not split ebuilds for openoffice, at least, nothing official (and I never heard of them on any overlay, but who knows).
From what I know, the core of openoffice is that monolithic that the benefit from compiling only a couple of the programs would be very little, since all the underlying code is shared anyway. I am not sure how complicated it would be. This has arised a few times on the past, but to tell the truth, it's been long since the last time I saw this same question, so maybe the situation has improved in which regards the OO modularity. But I have no real idea.
I guess that the real point (whatever the complexity of the problem is) is that no one cares enough to write the ebuilds and maintain them.
From what I know, the core of openoffice is that monolithic that the benefit from compiling only a couple of the programs would be very little, since all the underlying code is shared anyway. I am not sure how complicated it would be. This has arised a few times on the past, but to tell the truth, it's been long since the last time I saw this same question, so maybe the situation has improved in which regards the OO modularity. But I have no real idea.
I guess that the real point (whatever the complexity of the problem is) is that no one cares enough to write the ebuilds and maintain them.
I don't understand why is it such a big problem 
If Windows builds can manage split installations, an even rpm/deb/whatever else distro packages can, why Gentoo does not do it? Moreover, I disagree with you in the statement that OO.o code is so monolithic that it cannot be split (see above).
I'm considering opening a request to developers (just to ask for a reason why don't the provide split installs), will this bring any result, or shouldn't I bother doing this?
Thanks for the info anyway
If Windows builds can manage split installations, an even rpm/deb/whatever else distro packages can, why Gentoo does not do it? Moreover, I disagree with you in the statement that OO.o code is so monolithic that it cannot be split (see above).I'm considering opening a request to developers (just to ask for a reason why don't the provide split installs), will this bring any result, or shouldn't I bother doing this?
Thanks for the info anyway
That is really not relevant. As I said, it *could* be done. My whole point is whether you are going to gain something (besides several MB) that will justify the dev power required (when we are evidently lacking in other areas). At the end of the day, and as I said above, it all comes down to having or not developers that are interested in the feature. No one can force a developer to work on an area in which s/he has absolutely no interest, unless s/he's really bored.Ch00k wrote:I don't understand why is it such a big problem
Plus, modularity in the binary packages for windows or another linux distro has *nothing at all* to do with the modularity of the source code, which is what matters *here*, in Gentoo.
You could, but first I advice you to search the forums and bugs.gentoo.org first. I am sure that this question has arose several times in the past (how distant past I don't know). Like this one:I'm considering opening a request to developers (just to ask for a reason why don't the provide split installs), will this bring any result, or shouldn't I bother doing this?
Thanks for the info anyway
http://forums.gentoo.org/viewtopic-t-48 ... rt-25.html
Bear in mind that Gentoo is not a binary build, where you can easily split and package separate components. The nature of the source matters, and not to a little extent. There's very little point in splitting a package if to compile each individual component you have to build 99% of the sources of the package each time. In fact, it would be idiotic because to build all the separate components, or even just 2 of them, would take longer than building the whole suite. That is, unless the source can easily be split into separate and independent units in a sane and logical manner like kde can (i.e. OO-core + several other -smaller- packages).
Maintaining such a best in Gentoo is no candy either... It's a real pain considering the number of architectures and how the Gentoo users like to find a thousand ways to break an OS, and the OO build system is not the most solid around either.
its a big problem because OOo is a monolithic build. All parts of all components have common core (like MS-Office 95 iirc).Ch00k wrote:I don't understand why is it such a big problem
I'm considering opening a request to developers (just to ask for a reason why don't the provide split installs), will this bring any result, or shouldn't I bother doing this?
Thanks for the info anyway
What you are talking abt w.r.t. deb and windows is the ability to not install a handful of libraries - those libs that still would have had to have been built by debian/Ubuntu or windows...
openoffice.org-writer
depends on: openoffice.org-core
openoffice.org-calc
depends on: openoffice.org-core
...
Now go look at the file count and install size
writer: 21meg
dpkg -L openoffice.org-writer | wc -l
84
core:109 meg
dpkg -L openoffice.org-core | wc -l
227
Basically if you are building from source you have already gone out of your way to build the main part and those few libs specific for each "frontend" are just sugar.
sure maybe for OpenOffice-bin (with some USE flag's) but wtf for OpenOffice-src?
IF OOo ever sort out their fugly codebase and actually make it truely spit then sure but atm ...
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;
You might achieve some of your desired effect by editing the openoffice-bin ebuild. You can eliminate some of the rpm's that are unpacked here:
I actually have done just that in the past, but never went too overboard.
Code: Select all
for i in base binfilter calc core01 core02 core03 core04 core05 core06 core07 draw graphicfilter images impress math ooofonts ooolinguistic pyuno testtool writer xsltfilter ; do
rpm_unpack "${S}/${BASIS}-${i}-${MY_PV3}.${OOARCH}.rpm"
done