Posted Sep 1, 2008 20:44 UTC (Mon) by vmole
In reply to: Policy-respecting .debs?
Parent article: Bitten by the Red Hat Perl bug (InfoWorld)
Digging up the meaning of these is possible, and I've done it, but it's rather a lot of bother compared to the process of creating an RPM.
So the fact that Debian provides tools that point out mistakes in packaging is bad. Hmmm. Do you turn off compiler warnings that you don't understand?
I can't speak to the shared library issues, but the reason you don't ship .pyc files is so that the install system can build the python version specific .pyc files according to which versions are on the user's system. Also, you don't ship preprocessed man pages, right? And I don't know why you think python library files have to be executable; the ones on my system aren't. Finally, if these are real issues, you should discuss them on the Debian python list, where the experts are.
Finally, it should be noted that pretty much every item in Debian Policy is there for reason, for solving a real problem. They don't add stuff just to be difficult. Sometimes it's "do X because Y is wrong", and sometimes it's "We can do X or Y, either would be right, but we choose X." Consistency is worth something.
to post comments)