Dne 19.6.2010 09:20, Dave Plater napsal(a):
Yes this is vague, if a python module had been likened to a shared lib I would have understood immediately but now I understand after reading over a few times.
i have expanded the "naming policy" section. please let me know if anything is still unclear I'm lead to understand that this naming policy only applies to python modules that are designed to be used by programs other than the
On 06/22/2010 08:36 PM, Jan Matejek wrote: package that they came from, is this correct?
I've also stumbled upon the "Fixing python install paths" part of "Packaging/Fixing" and it is clear to me that the packages own install's default was correct in installing the py files to %python_sitelib. This also needs clarification in "Packaging/Python" or a link to the "Packaging/Fixing" part.
i'm not sure what you mean here - can you propose a specific change that would help with your problem?
I'm referring to the correct directory that the python modules from package ffado are installed in. In the package changelog there is mention of :- "All ffado stuff is now in packages getting installed to the official python dirs. Ideally this would allow other apps to use the stuff from us." and the default install directory is %{_libexec}/python%{py_ver}/site-packages. In "Packaging/Fixing" it indicates that this is the preferred directory but "Packaging/Python" isn't clear enough about which is the preferred directory, "Packaging/Fixing" is much clearer and the "File Lists" section should have a link to "Packaging/Fixing". Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org