[Debian-med-packaging] Bug#516037: gnumed-client: hard-codes the location to python modules
Karsten.Hilbert at gmx.net
Wed Feb 18 23:41:17 UTC 2009
On Thu, Feb 19, 2009 at 12:03:41AM +0100, Josselin Mouette wrote:
> the gnumed-client package uses a hard-coded path to the python modules:
Nope. It just uses this path to start the gnumed.py. All
module imports are relative to the systemwide modules
> However, because of numerous requests from developers, the installation
> path for these modules is going to change, so this will make
> gnumed-client fail.
We'll fix it.
> 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. Instead, I’d like to suggest alternate solutions
> that are independent from the packaging layers:
I'm in favour of that.
> * 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.
That script is shell because everything usefully done in
Python is done by gnumed.py.
> * Move part or all of the files to a private modules directory.
Hopefully we can find another way.
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
More information about the Debian-med-packaging