Package: pymol Version: 1.1-1 Severity: important Hi,
the pymol package uses a hard-coded path to the python modules: export PYMOL_PATH=/var/lib/python-support/python2.5/pymol/ However, because of numerous requests from developers, the installation path for these modules is going to change, so this will make pymol 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. 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. * Move the __init__.py script that you are actually executing to /usr/bin. There is no point in shipping it in a Python directory if it meant to be executed. * Move part or all of the files to a private modules directory. Thanks, -- .''`. 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.
signature.asc
Description: Ceci est une partie de message numériquement signée