It's generally good practice to include the autotools output (i.e. a working configure script) in release tarballs. That way users can just run ./configure without making sure that they have a full autotools setup that matches their expectations. It also means that missing packages will be correctly reported by ./configure rather than causing incomprehensible errors when running autogen.sh.
It's generally good practice to include the autotools output (i.e. a working configure script) in release tarballs. That way users can just run ./configure without making sure that they have a full autotools setup that matches their expectations. It also means that missing packages will be correctly reported by ./configure rather than causing incomprehensible errors when running autogen.sh.