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

Andreas Tille tillea at rki.de
Thu Feb 19 07:19:00 UTC 2009

On Thu, 19 Feb 2009, Josselin Mouette wrote:

> the gnumed-client package uses a hard-coded path to the python modules:
>        GNUMEDDIR=/var/lib/python-support/python${PYVER}/Gnumed/wxpython
> However, because of numerous requests from developers, the installation
> path for these modules is going to change, so this will make
> gnumed-client fail.
> If you really want to keep hard-coding this path, it is possible to
> handle this with a synchronized upload and a Breaks:, but I’d like to
> avoid it if possible.

I would like to follow your advise to not hardcode tha path.

> Instead, I’d like to suggest alternate solutions
> that are independent from the packaging layers:
>      * Detect the modules location dynamically from the script. You can
>        see an example in the pychecker package.
>      * Make /usr/bin/gnumed a python script, rewriting the environment
>        manipulations in python; this makes the import trivial.

What means "trivial".  Is there an alternative example like pychecker
for the first option?

>      * Move part or all of the files to a private modules directory.

If you ask me this sounds like the most reasonable suggestion.  But
how does it work together with python-support?  Any docs how the behaviour
of python-support will change?  (I haven't followed the debian-python
discussion very closely.)

Kind regards



More information about the Debian-med-packaging mailing list