I am moving the venue for this discussion on stdeb to the distutils-sig
(from http://bugs.python.org/issue1054967 ). I think this is better
discussed here.
On 4/29/10 9:23 PM, Barry A. Warsaw wrote:
Manual moving/copying is what I want to avoid. I'd be totally happy with not
reinventing the wheel if you think this would be easy to add to stdeb!
Specifically: just create debian/ in place and do not build package.
OK, I just added a new command "debianize" to stdeb (git commit 3cac5533
on github). This is currently in the "debianize" branch, which I intend
to merge into the master branch after a bit more review.
I have a few other minor suggestions, though if you think this isn't the best
place to track them, please let me know where to submit them.
In general, the place is "Issues" at http://github.com/astraw/stdeb ,
but I've addressed all the issues below.
* Add setup.py entry_points so you don't have to use --command-packages
This (and all other dependencies on setuptools) was removed at the
request of the distutils maintainer Tarek Ziadé, who suggested that
depending on setuptools prevented listing stdeb in the stdlib distutils
documentation. "--command-packages" is standard, documented distutils,
and works fine in my experience. If it's convenience you're after, you
can add this option to your ~/.pydistutils.cfg file as documented in the
stdeb README.rst file. I'm not planning on re-introducing the old behavior.
* Package: shouldn't change dots to dashes. E.g. flufl.enum should be called
python-flufl.enum
This should be fixed in git commit 24085bb.
* Update to Standards-Version: 3.8.3
Thanks for the alert. I'll have a look. Added to the tracker at
http://github.com/astraw/stdeb/issues/issue/25
I'm happy to test whatever you come up with.
Great. If you want to write unit testing infrastructure, that'd be great.
-Andrew
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
