On Sun, Feb 01, 2009 at 02:32:06PM +0900, David Cournapeau wrote:
Floris Bruynooghe wrote:
On Sat, Jan 31, 2009 at 10:37:56AM -0500, P.J. Eby wrote:
At 05:40 PM 1/31/2009 +0900, David Cournapeau wrote:
But you mostly do not need to care, as a developer: .py files would be considered as data files, extensions as arch-dependent, etc...
If this is true, then there's no need to distinguish between .py files and any other data files - they both belong in /share to begin with, not in /lib. Or else they ALL belong in /lib. The entire "FHS demands they be split" concept is wrong from the get-go, under that interpretation.
I don't think trying to split off .py and .so files is a good idea.
That's how it is done in debian and ubuntu packages. So if you want to make it easier for those distributions, you don't have a choice.
Hmm fair enough, I must have missed that last time I looked at the implementation of python-support and python-central. But both take the burden of having to create a symlink farm because of this though. And to be honest I think the motivation for this is supporting multiple python versions without having to duplicate all .py files rather then the FHS. But the great thing about the proposal is that it doesn't even matter. Files will be easily tagged/detected as "python modules" and "python extension modules" and the tools consuming this information can decide to do what they want with them. Regards Floris -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org