Marcus Harnisch writes:
Where I am stuck is the autoconf stuff. MMM has been converted to
autoconf between versions 0.4.7 (in our current package) and 0.4.8.
What about all those files? We have to ship the files for license
No. There's nothing in the GPL that says you have to ship everything
you receive. If we *do* ship something and it would normally be
considered a generated file (eg, configure), then we must ship the
corresponding source (for configure, configure.ac). But if we ship
configure.ac, we are not required to ship configure.
Whether we need to ship configure is determined by whether our users
would have any use for it in regenerating the package. What does it
do in the context of the XEmacs package system? If "nothing" because
all the work is done by XEmacs.rules and our Makefiles, no, we don't
need to ship it.
What do you mean by "all those files"? There should be a
"configure.ac" and a "configure". What else?
What about generated info files that are part of the upstream
I suppose we will regenerate them. Do we still include the
pregenerated files for legal reasons?
No. Again, we can throw away any generated files we want to.
XEmacs-Beta mailing list