Dne 18.6.2010 09:50, Ludwig Nussel napsal(a):
Why do such packages install files into the python file hierarchy (ie module search path) then?
because that's customary, convenient, and only drawback is this one rpmlint warning if packages installed their private modules into their own hierarchies, they would need to actively maintain knowledge about where they install, which has many drawbacks: - it limits flexibility of python and package install path - the packages themselves need to care about lib/lib64 distinction, or install into /usr/share (which as of now breaks FHS) - they would need to modify their sys.path, which is inconvenient and can cause problems with tools like virtualenv - they would need to express this in their build scripts (distutils install into python hierarchy by default) all in all: for many packages, this is too much trouble for too little gain as for the python naming policy, the wiki page seems pretty clear on that: "All python **modules**, whether pure python or C-based, should be called python-modulename. This policy doesn't apply to end-user applications written in python." (from http://en.opensuse.org/Packaging/Python#Naming_policy ) Emphasis added - the naming policy only applies to python modules, i.e. packages that provide functionality to other python programs. It does not apply to programs that only happen to install into python's hierarchy. If you think that the wording is unclear, or that we need clarifications about what constitutes a "module" and what is "end-user application", any suggestions are welcome. regards m. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org