On 30-Jan-2008, Stefan Bienert wrote: | now I got a last question to put the whole licensing-issue to an end. | If we use the autoconf stuff, with macros and all, internaly for the | development process (access to this resource only via private accounts) | but only include the configure script and makefiles in the distributed | package (making the software accessible to the public), it should be OK | to use our own license on the project. Right or not? Whether it impacts licensing or not, I think it's rather unfriendly to ship only the generated configure script and not the sources that generated it. It makes modifying the configure script difficult. jwe _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
