Daniel Stenberg <[EMAIL PROTECTED]> writes: > On Tue, 7 Aug 2007, Simon Josefsson wrote: > >> Can't we use a make target for this, rather than a script? I'm >> thinking 'make indent'. > > Yeah, sure. But I don't think people will use it uncondionally on a > lot of source files very often so it will make more sense to be used > like "./indent.sh mynewfile.c" or similar.
Or we could make 'make indent' on all files part of the release process. :) >> is there a reason for using the buildconf script rather than the >> recommended 'autoreconf --install'? > > Recommended by who/what? I've never seen nor used autoreconf! I > personally don't care much what we call the script, I just picked a > name I use in a few other projects. See: http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_chapter/autoconf_3.html#SEC14 I'm not convinced the order our current buildconf script runs the various auto*-tools is guaranteed to always end up in a usable state. There is some logic in the autoreconf tool that does the right thing in all cases. Thus, having our buildconf script contain: #!/bin/sh autoreconf --install should be sufficient, although we'll need to re-work how example/simple/config.h is handled. /Simon ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
