[Slackbuilds-users] OpenOffice 3 SlackBuild - Spell Checker broken
pc_warner at yahoo.com
Wed Oct 15 20:30:19 UTC 2008
You could just activate them in the doinst.sh, but then you would have extra files not in the package. I figured out that these extra files are located under
Perhaps the build script could add some of these files manually before tarring it up.
If nothing else a note in the README will suffice.
Thanks for your work on this, Robby. :)
--- On Wed, 10/15/08, Robby Workman <rw at rlworkman.net> wrote:
> From: Robby Workman <rw at rlworkman.net>
> Subject: Re: [Slackbuilds-users] OpenOffice 3 SlackBuild - Spell Checker broken
> To: slackbuilds-users at slackbuilds.org
> Date: Wednesday, October 15, 2008, 12:47 PM
> On Wed, 15 Oct 2008 13:31:36 -0500
> Robby Workman <rw at rlworkman.net> wrote:
> > On Wed, 15 Oct 2008 10:48:36 -0700 (PDT)
> > Phillip Warner <pc_warner at yahoo.com> wrote:
> > > Based on what Willy said maybe Robby should have
> all three installed
> > > in the doinst.sh. The one that would get used by
> default would be
> > > the one that matches the users language settings
> in OOo.
> > I don't see a *good* reason not to just install
> all of them, unless of
> > course they add lots of space to the package. I
> don't think that will
> > be the case, as they obviously ship with the package -
> they're just
> > not activated for whatever reason.
> > The problem now is to figure out a way to
> "activate" them inside the
> > package DESTDIR before it's tgz'd up.
> To reply to myself:
> liberty $ ./unopkg --help
> using: unopkg add <options> extension-path...
> unopkg remove <options>
> unopkg list <options> extension-identifier...
> unopkg reinstall <options>
> unopkg gui
> unopkg -V
> unopkg -h
> add add extension
> remove remove extensions by identifier
> reinstall expert feature: reinstall all
> extensions list list information about
> extensions gui raise Extension Manager
> User Interface (GUI)
> -h, --help this help
> -V, --version version information
> -v, --verbose verbose output to stdout
> -f, --force force overwriting existing
> --log-file <file> custom log file; default:
> --shared expert feature: operate on shared
> run only when no
> Office process(es) are running!
> --deployment-context expert feature: explicit
> deployment context
> For details concerning deployment and this tool, please
> read the
> developer's guide:
> I suspect that the solution to this is buried in that link
> but I can't get there at the moment, because the OOo
> website is being
> hammered, they say. Oh well.
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives -
> FAQ - http://slackbuilds.org/faq/
More information about the SlackBuilds-users