On 01/31/12 01:41 PM, Brian Cameron wrote:
In other words, if you build a module with automake that does not have
a COPYING file, it adds a GPLv3 one for you.
It might make more sense to make automake use "foreign" strictness on
Solaris by default instead of "gnu" strictness, so it avoids doing this.

I don't think changing automake behavior like this from upstream buys anything
but confusion, and can lead to mistakes being made either way - someone working
on a module on Solaris publishes their sources out to the world and finds out
later the rest of the world thought they'd chosen GPLv3 since that's what they
saw when running automake on Linux, BSD, etc. using the published sources.

--
        -Alan Coopersmith-        [email protected]
         Oracle Solaris Platform Engineering: X Window System

_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss

Reply via email to