-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guillaume Melquiond schrieb: > On 2009/2/22, Nils Kneuper wrote: > >> The point is *really* simple: >> >> To generate a tarball that works for endusers when using autotools, autotools >> have to be used to generate it, or there is no plan configure file. No way to >> just use svn export and be done. > > Why not? Both cmake and scons require the users to have them installed > before they can use these build systems. None of them work just by > simply doing svn export. So why not assume the same for autotools? Why > not require users who want to use autotools to have them installed? > > I have a hard time seeing why removing a few text files will suddenly > make "svn export" a lot simpler.
The basic reason is that when autotools are used, users *expect* to find configure files and do not expect to run ./autogen.sh first. When using scons or cmake to build users know that they have to install it separately. Even more important (to me) is that as long as we use autotools as build system users probably expect configure to be there and that they can go on as before. When announcing that autotools (and thus configure) are no longer supported, they know that something changed and they got to adopt. Yes, in theory it *should* be identical if all users had a satisfying version of autoconf and automake installed on their boxes. Then there would be no problem when just shipping a clean svn export. I am a little hesitant to do so when not explicitly stating "completely forget about autotools". I hope you understand what I want to say with the stuff above. Cheers, Nils Kneuper aka Ivanovic -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmhfWEACgkQfFda9thizwXb4gCfYkb0GfaqILrPXOIzjGJsxlmf kl8AnRsomaO3do6Sq2GT7ifsEzq7n6z4 =hyxI -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
