Robert Wuest wrote:
> Note that I am not calling it a problem, but it is a
> situation that all Vtcl users should be aware of: as the license stands
> now, if you use Vtcl to develop a program, that program must use the
> GPL.
That's how the GPL is _supposed_ to work.
> Whether that limits the usefulness or acceptance of Vtcl is beyond me
> and is an issue for the developers to decide.
My 5c worth (no 2c pieces in Oz any more):
In the real world, it raises some political difficulties
(proprietary-oriented managers, lawyers etc have a cow) but very few
practical ones.
Most proprietary applications are at least 95% non-secret code anyway,
and it's usually possible to use proprietary glue to stick together GPL
components; for example, use vTCL to make all of the UI bits but keep
some of the logic in separate files and either treat those files as
libraries, or have them treat the vTCL-generated TCL as libraries.
Issues which could remain sticky are things like ``does including our
corporate logo within a vTCL-generated panel automatically GPL it?'' and
even this kind of thing can be worked around by using a placeholder
during development and shipping the real logo in a separate archive
(with all of your proprietary glue logic) and bearing in mind that
``mere aggregation'' on a common medium does not a GPLing make.
Cheers.
--
Sometimes I lie awake at night, and I ask, "Where have I gone wrong?"
Then a deep voice says to me, "This is going to take more than one
night." -- Charlie Brown, "Peanuts" [Charles Schulz]
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/vtcl-user
