However, what if we compose a special FreeDOS License, best suited to our needs (saying everything about executable packers, library code, inline compiler code, embedded systems use, and so on - all issues that are NOT satisfactory solved by the GPL, for example the ethernal question of the distinction between "combining" and "aggregation", WITHOUT the GPL virus effect), so this "FreeDOS License" becomes yet another item in the following rather long list of GPL-compatible licenses? This way we will NOT depend on what anyone else thinks is good or bad, but will depend only on our OWN vision.
I am for that, because this way we can get rid of at all of these issues about linking, stubbing to non GPL or composing software using tools that are not GPL. However, I have not read in depth all these licenses that you mention, where to start with?
I found this page convenient as a starting point: http://www.gnu.org/licenses/license-list.html
Also how many other people here share this point?
I don't know. People, please express your opinion!
Lucho
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
