Prev: slackfind.net
Next: Annoying behaviour korganizer?
From: Vwaju on 10 Mar 2010 10:05
I upgraded to Slackware 13.0, and I need to reinstall Open Office.
When I did this under 12.2, I just used the procedure in the Set-Up
Guide at http://documentation.openoffice.org/setup_guide2/index.html#12
(which contains detailed instructions for installing to Slackware).
This seemed to work pretty well.

I see, though, that you can download a Slackbuild script from
slackbuilds.org and compile Open Office on your own computer.

What are the reasons (pro or con) for doing one rather than the other?

Thanks & Best Regards,

Vwaju
New York City
From: Ed Wilson on 10 Mar 2010 11:24
Vwaju wrote:

> I upgraded to Slackware 13.0, and I need to reinstall Open Office.
> When I did this under 12.2, I just used the procedure in the Set-Up
> Guide at http://documentation.openoffice.org/setup_guide2/index.html#12
> (which contains detailed instructions for installing to Slackware).
> This seemed to work pretty well.
>
> I see, though, that you can download a Slackbuild script from
> slackbuilds.org and compile Open Office on your own computer.
>
> What are the reasons (pro or con) for doing one rather than the other?
>
> Thanks & Best Regards,
>
> Vwaju
> New York City

I think the Slackbuild basically does the same things as the instructions
you linked, namely converting the RPMs into a proper Slackware package. One
difference however is that the Slackbuild creates one package out of the
many RPMs instead of converting them independently as the setup guide
suggests.


--
Ed

From: tapp on 10 Mar 2010 11:36
Not an answer to your question, but if you want to be done with it
quickly, just use Mr. Workman's packages: http://rlworkman.net/pkgs/
From: King Beowulf on 12 Mar 2010 10:49
On Wed, 10 Mar 2010 07:05:29 -0800, Vwaju wrote:

> I upgraded to Slackware 13.0, and I need to reinstall Open Office. When
> I did this under 12.2, I just used the procedure in the Set-Up Guide at
> http://documentation.openoffice.org/setup_guide2/index.html#12 (which
> contains detailed instructions for installing to Slackware). This seemed
> to work pretty well.
>
> I see, though, that you can download a Slackbuild script from
> slackbuilds.org and compile Open Office on your own computer.
>
> What are the reasons (pro or con) for doing one rather than the other?
>
> Thanks & Best Regards,
>
> Vwaju
> New York City

The SBo slackbuild creates a proper Slackware package from the binary
rpm. This slackbuild also cleans up the install a bit (redundant fonts,
file locations).

You could use the OO installer and procdeure, but then upgrading is a of
a hassle. I don't think you want to actually compile OO - from what I
understand that is a full time job.
From: Henrik Carlqvist on 12 Mar 2010 15:23
King Beowulf <kingbeowulf(a)gmail.com> wrote:
> The SBo slackbuild creates a proper Slackware package from the binary
> rpm.

> I don't think you want to actually compile OO - from what I
> understand that is a full time job.

Been there, done that, mostly for fun... When I finally got OO compiled
after installing different strange java-dependencies it turned out that
the compiled OO ended up as rpm files and not as executables which could
be installed with something like "make install". So even though compiling
from source I ended up installing rpm files, duuuh... This was with
OpenOffice 2.0.2, maybe things have changes since then.

I got my build procedure for OO 2.0.2 somewhat documented at
http://makepack.sourceforge.net/rule_guide.shtml . What the file on the
page does is: First installs all the dependencies listed as DEPS, then
unpacks the source archive and configures it with CONFIGURE_METHOD and
builds it with BUILD_METHOD. Finnaly it is installed with the described
INSTALL_METHOD.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

 | 
Pages: 1
Prev: slackfind.net
Next: Annoying behaviour korganizer?