[Debian-med-packaging] Bug#516037: gnumed-client: hard-codes the location to python modules
joss at debian.org
Wed Feb 18 23:03:41 UTC 2009
the gnumed-client package uses a hard-coded path to the python modules:
However, because of numerous requests from developers, the installation
path for these modules is going to change, so this will make
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:
* 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.
* Move part or all of the files to a private modules directory.
.''`. Debian 5.0 "Lenny" has been released!
: :' :
`. `' Last night, Darth Vader came down from planet Vulcan and told
`- me that if you don't install Lenny, he'd melt your brain.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Ceci est une partie de message
Url : http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20090219/363f7f66/attachment-0002.pgp
More information about the Debian-med-packaging