🚀 go-pugleaf

In article <1imlr5INN2tu@early-bird.think.com> barmar@think.com (Barry Margolin) writes:

   The simple way to avoid the GPL "virus" problem on your own work is to
   apply the GPL to the copy rather than the original, i.e. write a program
                        ^^^^
   and make it proprietary, make a copy of it (as the owner, you have this
                                   ^^^^
   right), and slap the GPL on this copy.  Derivatives of the copy must
                                    ^^^^                      ^^^^
   inherit the GPL, but derivatives of the original can be subject to any
   terms you wish.

As I posted in response to a mib posting, I suggest that instead of "copy"
you really mean "derivate work" [based on the original].

And the fact that a derivative work is, in this case, identical to the
original, and hence not truly derivative, shows the fallacy of believing
that one loses the copyright to one's own work by releasing it under the
GPL.  You lose only the ability to restrict recipients of the GPL-protected
version so they can't share copies with their neighbors.
--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu
Member of the League for Programming Freedom (LPF) lpf@uunet.uu.net