> We do not use autoreconf, nor do I know what it does. http://www.gnu.org/software/hello/manual/autoconf/autoreconf-Invocation.html http://linux.die.net/man/1/autoreconf
> If it is something that is important, then the command must be fixed. I hope that it will become easier to regenerate configure scripts also for your software project. > Perhaps you mean "will configuration script changes be permitted". One of the templates was updated recently. ;-) http://bacula.git.sourceforge.net/git/gitweb.cgi?p=bacula/bacula;a=history;f=bacula/autoconf/configure.in;h=9fe131f1aa189b15ebc82a9e62f77ec615caeeb3;hb=HEAD > The answer is yes, providing they are necessary and they are not thousands of > lines at a time. I guess that the proposed move of the configuration templates hides somehow other potentially interesting adjustments in the "git format-patch" data. > We are not prepared to add massive changes that just rewrite the code without > adding new features. We will accept small patches that clean up old or out > of date code. I guess that it will be more important to achieve a common understanding and an agreement on each item that I mentioned in my bug report before corresponding changes will only be expressed in the source file language. http://bugs.bacula.org/view.php?id=1415 Regards, Markus ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
