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

Andreas Tille tillea at rki.de
Thu Feb 19 08:31:52 UTC 2009

On Thu, 19 Feb 2009, Karsten Hilbert wrote:

> The "trivial" seems to come about by the misbelief that our
> module imports somehow use GNUMEDDIR which they do not.
> That's only used to access gnumed.py, nothing else.
> gnumed(.sh) is there exactly to *be* a shell wrapper around
> gnumed.py to allow the user to run additional shell scripts
> before launching GNUmed. It doesn't make any sense to
> convert it to Python.

So the fix for the bug is really simple: Install the Python
modules at *any* place which the Pathon policy suggests and
adapt the shell script to this place, right?

Kind regards



More information about the Debian-med-packaging mailing list