Dave Malcolm <dmalc...@redhat.com> added the comment: Eric Smith: > Isn't it true that after regenerating configure that you need to check > it back in? Or is that so obvious to everyone except me that it's not > worth mentioning? FWIW the above point wasn't obvious to me; if that's the case, then it needs to be spelled out.
My perspective here is as a developer without commit rights to svn; I'm developing patches to be attached to the issue tracker, and occasionally they require changing configure.in BTW, should the changes to the generated "configure" be excluded from such patches, or should they be included? (to what extent do they contain meaningful information during review?) Mark Dickinson: > Eric: interesting point. Without having thought about it, I was > assuming this was about regenerating configure and pyconfig.h.in in > your own working copy (e.g., because you want to test locally some > configure script changes) rather than regenerating the configure > script in the central repository. That's roughly what I was doing, yes; sorry for any confusion. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7997> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
