This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients alberanid, anadelonbrin, astraw, barry, dairiki, ebfe, eric.araujo, jafo, kbk, leonidasxiv, loewis, rockstar, tarek
Date 2010-04-27.20:14:26
SpamBayes Score 2.5434645e-06
Marked as misclassified No
Message-id <1272399269.44.0.478171811957.issue1054967@psf.upfronthosting.co.za>
In-reply-to
Content
Hello

There has been a number of discussions about bdist_deb, and some code too. I don’t have links handy, unfortunately, but I remember a conclusion that was: Don’t.

 Debian packages are best made by Debian tools, which go to great lengths to comply with Debian Policy, work together, and are frequently updated. On the Distutils(2) site, the most we can do would be a bdist_dsc command that produces a special file which is used by debianizing tools.

 A key thing to remember is that .deb is not just a file format, it’s the embodiment of a Policy (the real value of Debian is its policy, not its package manager—a nice technical side effect), and as such, best handled by Debian tools.

Disclaimers: I’ve not been following packaging discussions for long, these lines are a summary of other people’s thoughts, I’m not a Debian developer or maintainer.

Cheers
History
Date User Action Args
2010-04-27 20:14:29eric.araujosetrecipients: + eric.araujo, loewis, barry, kbk, jafo, anadelonbrin, astraw, dairiki, alberanid, leonidasxiv, tarek, rockstar, ebfe
2010-04-27 20:14:29eric.araujosetmessageid: <1272399269.44.0.478171811957.issue1054967@psf.upfronthosting.co.za>
2010-04-27 20:14:27eric.araujolinkissue1054967 messages
2010-04-27 20:14:26eric.araujocreate