I'm about to release a GPL licensed application framework and am planning on dual-licensing with a proprietary license. I'm wondering if the GPL classpath exception could be used as a basis for a simple license.
I would like the ability to separate support contracts and other typical proprietary software license clauses, indemnities and such, from the simple permission to write proprietary software using the framework.
The following example text is based on the GPL linking exception.
The copyright holders of this library give COMPANY permission to link VERSION of this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of their choice, provided that COMPANY also meets, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. COMPANY may not extend this permission to its version of the library, whether the library has been modified or not.
Is this viable? Any pros or cons?