Author eric.araujo
Recipients alberanid, anadelonbrin, astraw, barry, dairiki, ebfe, eric.araujo, jafo, kbk, leonidasxiv, loewis, rockstar, tarek
Date 2010-04-29.20:16:26
SpamBayes Score 9.57248e-08
Marked as misclassified No
Message-id <4BD9E904.3000509@netwok.org>
In-reply-to <1272569727.29.0.818992050397.issue1054967@psf.upfronthosting.co.za>
Content
Barry, IIUC you want the “debian” command to create a debian source
package, which can be converted to debian binary package(s), checked and
uploaded with standard tools. Perfect.

Andrew, I am uncomfortable with stdeb. (Trying to express respectful
constructive critique, not just picking on your project.) The version in
Debian testing, 0.5.1-1, still requires setuptools (actually only
pkg_resources, which is split into another package in Debian, for space
or politic reasons). The py2dsc script seems to be obsoleted by the
to-be “debian” command. The pypi-install script seems dangerous to me,
because downloading unverified software and putting it into the system
seems a rather bad idead (a.k.a. “sudo ./setup.py install considered
harmful”).

python-debian provides useful support code for generating and reading
debian formats. A quick read show the code would benefit from some 2.6
modernizing (i.e. gain in simplicity and readability by using modern
idioms and stdlib functions). Would using this package in stdeb /
distutils2.command.debian instead of shelling out bring anything?

(Sorry about the badly wrapped paragraph I forgot to remove in my
previous message. And sorry to write so much words instead of code ;)

acute-accent-ly yours
History
Date User Action Args
2010-04-29 20:16:28eric.araujosetrecipients: + eric.araujo, loewis, barry, kbk, jafo, anadelonbrin, astraw, dairiki, alberanid, leonidasxiv, tarek, rockstar, ebfe
2010-04-29 20:16:27eric.araujolinkissue1054967 messages
2010-04-29 20:16:26eric.araujocreate