[Debian-med-packaging] Bug#516037: gnumed-client: hard-codes the location to python module

Andreas Tille tillea at rki.de
Fri Feb 20 14:34:35 UTC 2009

On Fri, 20 Feb 2009, Karsten Hilbert wrote:

> The attached script would be my suggestion. If that looks OK
> I will commit it to the upstream CVS.

Looks perfectly reasonable to me.  Do you want me to fix this
problem now by uploading just another 0.3.10 based Debian package
or do you think it makes sense to wait for the upcoming 0.4.
IMHO there is no need to hurry because there is no problem with
the *currently* existing packages in unstable.

Kind regards


-------------- next part --------------

# This shell script is intended to be placed in
# /usr/bin/ and should be run to start a GNUmed
# client.
# $Source: /sources/gnumed/gnumed/gnumed/dists/Linux/gnumed,v $
# $Id: gnumed,v 1.21 2009/02/20 10:45:44 ncq Exp $
# license: GPL
# Karsten Hilbert, Sebastian Hilbert, Andreas Tille

# for debugging this script
# set -x


# The system-wide configuration file for backend profiles.
if [ ! -e ${SYSCONF} ] ; then
	echo "Global config file ${SYSCONF} missing."
	exit 1

# source systemwide startup extension shell script if it exists
if [ -r /etc/gnumed/gnumed-startup-local.sh ] ; then
	. /etc/gnumed/gnumed-startup-local.sh

# source local startup extension shell script if it exists
if [ -r ${HOME}/.gnumed/scripts/gnumed-startup-local.sh ] ; then
	. ${HOME}/.gnumed/scripts/gnumed-startup-local.sh

# now run the client
python -m Gnumed.wxpython.gnumed ${OPTIONS}

# sync the discs just in case

More information about the Debian-med-packaging mailing list