Re: [Gnumed-devel] GNUmed Live CD supports OpenOffice and Latex

[Sebastian Hilbert]

Am Dienstag 27 April 2010 14:48:38 schrieben Sie:
> Hi,

Hi,

Thanks for your email ( see his comments below my original message).
I have forwared your mail to the GNUmed developer list for better making use 
of your suggestions.

I am very glad we now have a contact regarding this issue as is will make the 
user experience much more pleasant.

I am forwarding your email to the Debian-med list as well since you state that 
your solution might fix the problem for other distros as well.

You say you are responsible for the packages. Do you happen to have any 
contacts to the people working on uno as we have some questions regarding 
making most of it from within GNUmed ?

Best regards,
Sebastian

> 
> I maintain the OOo packages for openSUSE and have another suggestion how to
> find the missing uno.py and unohelper.py. It should actually fix the
> problem also for other distros.
> 
> On Wednesday 21 April 2010, Sebastian Hilbert wrote:
> > Hi all,
> > 
> > GNUmed Live CD now has OpenOffice and Latex fully working. That way users
> > can have a look at the correspondence feature of GNUmed.
> > 
> > Live CDs and vmware image will appear at
> > https://sourceforge.net/projects/gnumedlive/
> > 
> > tomorrow. Debian based Live-CD will appear as soon as packages for 0.7.1
> > hit Debian Sid.
> > 
> > BTW: python-uno is working out of the box on Debian but for other distros
> > a little effort is needed.
> > 
> > For openSUSE it starts working when creating two symlinks like that:
> > 
> > ln -s /usr/lib/ooo3/basis-link/program/uno.py /usr/lib/python/uno.py
> > ln -s /usr/lib/ooo3/basis-link/program/unohelper.py
> > /usr/lib/python/unohelper.py
> 
> I do not like these symlinks. I do not see other .py files
> in /usr/lib/python/ on openSUSE...
> 
> I think that the official cross-platform way to find the OOo uno components
> is the following:
> 
>       + find the OOo installation via the /usr/bin/soffice symlink, see
>           the section "Finding a UNO installation" at
> http://udk.openoffice.org/common/man/spec/transparentofficecomponents.html
> 
>       + set the PYTHONPATH, JAVAPATH. LD_LIBRARY_PATH accordingly
> 
> 
> For example, I use the following code in the ooconvert script. It uses the
> python UNO, so we need to set the PYTHONPATH:
> 
> # detect the OOo installation
> ooo_home=
> soffice=`which soffice 2>/dev/null`
> if test -L $soffice ; then
>     soffice_path=`readlink $soffice`
>     ooo_home=`dirname $soffice_path`/..
> fi
> 
> # try some fallbacks
> if test -z "$ooo_home" ; then
>     for dir in /usr/lib64/ooo3 \
>                /usr/lib/ooo3 ; do
>         test -f "$dir/program/soffice" && ooo_home="$dir" && continue
>     done
> fi
> 
> if test -z "$ooo_home" ; then
>     echo "Error: Unable to find OpenOffice.org instalation"
>     exit 1;
> fi
> 
> export PYTHONPATH="$ooo_home/basis-link/program"
> 
> 
> Please, add me into CC because I am not on this list. A friend pointed me
> to this particular mail...