Re: licenses in generated m4 files

[Peter Simons]

Alexandre Duret-Lutz writes:

 > [various points]

I think it's better to agree to disagree than to continue
discussing this. IMHO, it is highly unlikely that anyone's
opinions will be changed no matter how long we continue to
argue, so I'd like to focus on the solution instead.


 >> (1) How does the author choose which license his macro is
 >> under? How does the markup format specify this
 >> information?

 > Wouldn't allowing free text at the top of the macro do
 > the trick?

Allowing a free-text field for the license essentially
equals allowing the author to choose any license he wants.
In the general case, however, that's not possible because
not all licenses are compatible with each other. I don't
feel qualified to read an arbitrary license and spot that
kind of thing, hence I'd be greatly in favor of limiting the
set of supported licenses to those that are known not to
conflict.


 >> (2) Which licenses do we accept?

 > Anything that is compatible with the license of the
 > archive itself.

Which licenses are? I'll need some sort of "comprehensive"
list.


 >> (3) What does the generated m4 source look like for each
 >> respective license we support?

 > That one is easy: exactly the same as the submitted
 > source :)

See my answer to (1).

Peter