[Libreoffice] Installation instructions for source code release
ftigeot at wolfpond.org
Sat Jan 29 02:29:24 PST 2011
Thanks everyone for your answers.
On Fri, Jan 28, 2011 at 10:03:42AM +0000, Michael Meeks wrote:
> On Fri, 2011-01-28 at 10:27 +0100, Francois Tigeot wrote:
> > Well, I may become a package maintainer in the future but for that I need
> > to be able to build LO from the released sources first.
> Sure ;-) so what I suggest you do is take a look at eg. Rene's debian
> packages, or Caolan's RedHat ones - that do a straight-through build,
> and get inspired by them ;-) try here:
Eric Hameleers from Slackware has also some interesting scripts:
> > Git is fine for real development but I'm afraid it may be too steep for
> > me now; I'd like to play it safe, try to build a somewhat stable version
> > without too much bugs. Maybe write a patch or two if something doesn't work.
> Sure, sure - but I think you will find (with the pace of change), that
> working on master is better: it is already easier to build master than
> 'stable' (though it does break occasionally), and it is far easier to
> create a patch to submit from git: "g diff" will extract all your
> changes, vs. having to do some diff -r's :-)
In the end, I could not build LO from the released tarballs. I have bitten
the bullet and now use git ;)
I'll send my first patch in a separate mail.
> Sure - and we are trying to fill out this niche; primarily by moving
> (slowly) towards a split build [ in fact openSUSE does this already ],
> whereby you can re-build and develop only one piece at a time - which is
> quicker: ie. just re-compile 'writer'.
That sure would be great ! I remember painfully 15-hours compilation times
in the days of OpenOffice 2.x ...
> Which is (at root) the background as to why there are so many things to
> download ;-) - just a result of that work being in progress still.
Is there any explanation on this process ? I've only found small notes
in the wiki.
More information about the LibreOffice