On Thu, Aug 24, 2006 at 05:56:07PM +0300, Lars Wirzenius wrote: > installed, can't be put into the Policy. The Policy editor, and those of > use who don't want to use debhelper, insist that writing policy based on > debhelper tools is not acceptable.
Not just those who don't want to use debhelper. Policy is, and has always been, written in terms of how dpkg works. Nothing more. It would be a very bad idea to change that, if only because somebody might have a nice idea for a build tool that would supersede debhelper. While it is, IMHO, perfectly acceptable to insist that people use some debhelper tool if they want to package something pythonesque, it is not acceptable to not document how they are *supposed* to work. -- <Lo-lan-do> Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
