On 06/23/2010 06:02 PM, Jan Matějek wrote:
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
package that they came from, is this correct?
yes, pretty much
Referring to this section :- In case you really need to specify your files by hand, there are two useful macros: * %python_sitelib expands to /usr/lib/pythonX.Y/site-packages. This is the install location for platform-independent modules. * %python_sitearch expands to %{_libdir}/pythonX.Y/site-packages, that is, either /usr/lib or /usr/lib64, depending on your architecture. This is the install location for platform-dependent modules. I'm not sure what a platform dependent python file is, this needs an explanation. All scripts must be noarch, therefore a .py file would go in %python_sitelib, which files would go into %python_sitearch?
I don't think that it's a good idea to link to Packaging/Fixing from Packaging/Python - IMHO, much better solution is to expand Packaging/Python and direct Packaging/Fixing into a specific section of it. There is already a section called "File locations" which says that " All python source and bytecode files should go into /usr/lib(64)/pythonX.Y/site-packages, or maybe /usr/lib(64)/yourapp." Do you think that this statement needs more emphasis or clarification?
Plus, the overall policy is that "files should generally go wherever upstream installs them, unless that conflicts with some of our policies". Would it help to mention this in the guidelines?
thanks m.
Definitely mention "files should generally go wherever upstream installs them, unless that conflicts with some of our policies" I maintain a few packages which use %_datadir/%name for their python scripts, ffado is the first one that uses %python_sitelib. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org