I've added a little bit to http://fedoraproject.org/wiki/OpenOffice.org
to document the best recipe for installing and deinstalling
openoffice.org extensions to avoid some gotchas. The example taken is
that of writer2latex and also shows the (submitted upstream) enhancement
to register an extension by linking to an the unzipped package to avoid
the vanilla behaviour of copying the package during installation.
C.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
01-04-2008, 06:10 PM
Rahul Sundaram
howto package openoffice.org extensions
Caolan McNamara wrote:
On Fri, 2008-01-04 at 09:06 -0900, Jeff Spaleta wrote:
On Jan 4, 2008 4:02 AM, Caolan McNamara <caolanm@redhat.com> wrote:
I've added a little bit to http://fedoraproject.org/wiki/OpenOffice.org
to document the best recipe for installing and deinstalling
openoffice.org extensions
that's great guidance. can we work this into the packaging guidelines
as a special case?
http://fedoraproject.org/wiki/Packaging/Guidelines
Section 40: Application Specific Guidelines
Sure, I hadn't sufficient mojo to edit that page of course, so feel free
to add a link to the extensions section or whack it into whereever it
should go.
Packaging Committee has instructions on changing the guidelines.
http://fedoraproject.org/wiki/Packaging/Committee
Rahul
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
01-04-2008, 06:16 PM
Caolan McNamara
howto package openoffice.org extensions
On Fri, 2008-01-04 at 09:06 -0900, Jeff Spaleta wrote:
> On Jan 4, 2008 4:02 AM, Caolan McNamara <caolanm@redhat.com> wrote:
> > I've added a little bit to http://fedoraproject.org/wiki/OpenOffice.org
> > to document the best recipe for installing and deinstalling
> > openoffice.org extensions
> that's great guidance. can we work this into the packaging guidelines
> as a special case?
> http://fedoraproject.org/wiki/Packaging/Guidelines
> Section 40: Application Specific Guidelines
Sure, I hadn't sufficient mojo to edit that page of course, so feel free
to add a link to the extensions section or whack it into whereever it
should go.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
01-07-2008, 10:12 AM
Alex Lancaster
howto package openoffice.org extensions
On Jan 4, 2008 4:02 AM, Caolan McNamara <caolanm@redhat.com> wrote:
[...]
>> http://fedoraproject.org/wiki/OpenOffice.org
>>>> to document the best recipe for installing and deinstalling
>>>> openoffice.org extensions
[...]
>>>>> "RS" == Rahul Sundaram writes:
RS> Packaging Committee has instructions on changing the guidelines.
RS> http://fedoraproject.org/wiki/Packaging/Committee
Caolan, do you have any best practices recommendations for the naming
of the openoffice.org extensions? It would be nice to add them to the
guidelines (then perhaps submit them to the packaging committee) e.g.,
I'd like to package ooolatex:
http://ooolatex.sourceforge.net/
and so should the package should (following the emacs-, python-,
perl-, R- convention) be called "openoffice.org-latex"? or should be
called "openoffice.org-ooolatex", or just "ooolatex"?
Also, will this particular extension, which is packaged as an .oxt
file, be able to be installed using the unopkg tool as suggested on
that page? i.e. are .oxt files intended to be installed using the
unopkg tool?
Any suggestions welcomed.
Alex
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
01-07-2008, 10:33 AM
Caolan McNamara
howto package openoffice.org extensions
On Mon, 2008-01-07 at 04:12 -0700, Alex Lancaster wrote:
> Caolan, do you have any best practices recommendations for the naming
> of the openoffice.org extensions?
I've no real strong feelings one way or the other, I found it convenient
for e.g. writer2latex which had multiple subpackages where one of them
was the openoffice.org extension to call that subpackage
openoffice.org-FOO, I guess just use your own judgement here.
> Also, will this particular extension, which is packaged as an .oxt
> file, be able to be installed using the unopkg tool as suggested on
> that page? i.e. are .oxt files intended to be installed using the
> unopkg tool?
Oh yes, you can just do
unopkg add --shared OOoLatex-4.0.0-beta-2-linux.oxt
-env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1
or if you want to use the linking mechanism to avoid duplicating the
contents of that .oxt at registration time then you can use something
like
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
01-07-2008, 10:43 AM
Alex Lancaster
howto package openoffice.org extensions
>>>>> "CM" == Caolan McNamara writes:
CM> On Mon, 2008-01-07 at 04:12 -0700, Alex Lancaster wrote:
>> Caolan, do you have any best practices recommendations for the
>> naming of the openoffice.org extensions?
CM> I've no real strong feelings one way or the other, I found it
CM> convenient for e.g. writer2latex which had multiple subpackages
CM> where one of them was the openoffice.org extension to call that
CM> subpackage openoffice.org-FOO, I guess just use your own judgement
CM> here.
OK, I didn't realise that writer2latex had non-OOo components, but
that makes sense.
>> Also, will this particular extension, which is packaged as an .oxt
>> file, be able to be installed using the unopkg tool as suggested on
>> that page? i.e. are .oxt files intended to be installed using the
>> unopkg tool?
CM> Oh yes, you can just do unopkg add --shared
CM> OOoLatex-4.0.0-beta-2-linux.oxt
CM> -env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1
CM> or if you want to use the linking mechanism to avoid duplicating
CM> the contents of that .oxt at registration time then you can use
CM> something like
Thanks for the suggestions. Is the "net.sourceforge.ooolatex"
something you derived from the webpage, or is that somehow also in the
.oxt?
Also, in this case it appears that upstream insists on including some
binaries in the .oxt file (they don't seem to distribute a true
OS-independent source tarball)
I assume the thing to do in the case is simply remove the files in
bin/ and lib/ after installing them in the %install section as you
describe above is the best way to deal with those? (libEMF is already
in Fedora, and I'd need to package latex2emf separately).
Alex
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
01-07-2008, 10:56 AM
Caolan McNamara
howto package openoffice.org extensions
On Mon, 2008-01-07 at 04:43 -0700, Alex Lancaster wrote:
> Thanks for the suggestions. Is the "net.sourceforge.ooolatex"
> something you derived from the webpage, or is that somehow also in the
> .oxt?
Actually I just unopkg add'ed it and then unopkg list --shared and
looked at what was the name of the extra extension listed there to
figure out what OOoLaTeX called itself. I could probably have
alternatively found that out by grovelling through the code.
> Also, in this case it appears that upstream insists on including some
> binaries in the .oxt file (they don't seem to distribute a true
> OS-independent source tarball)
> 21150 11-01-07 12:42 bin/Linuxi386/latex2emf
> 28692 11-01-07 12:43 bin/Linuxppc/latex2emf
> 710928 11-01-07 12:41 lib/i386/libEMF.so.1
> 717884 11-01-07 12:40 lib/ppc/libEMF.so.1
> -------- -------
> 1676064 35 files
>
> I assume the thing to do in the case is simply remove the files in
> bin/ and lib/ after installing them in the %install section as you
> describe above is the best way to deal with those?
That should work I'd say, assuming that the package hasn't hardcoded
those paths into itself somewhere, pity that the upstream doesn't have a
pure source package but seeing as it just looks like a hack to have
latex2emf available for execution by some starbasic code we'll probably
get away with it.
C.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
howto package openoffice.org extensions
