Date:	Tue, 15 Mar 94 18:23:43 -0500
From:	dj AT ctron DOT com (DJ Delorie)
To:	darrylo AT sr DOT hp DOT com
Cc:	babcock AT cfa DOT harvard DOT edu, djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Distributing a recompiled GO32

>      I'd like some clarification, too.  OEmacs has been distributing a
> modified go32.exe, and I've never heard any concerns about this.

You ship sources.  No problem.  Ignore the confusion and trust the
force Luke (bzzrt...sorry) .%. trust the COPYING.DJ file.

> However, DJ said, in a different message (referring to GO32):
> 
> 	No, only the binary that *I* distribute may be redistributed.  That

Clarification: . . . redistributed *without sources* (but with pointer
to djgpp as per copying.dj).

> I'm confused.  If DJ feels this way, why hasn't he (you) told me about
> this?  [ Hmmm.  Unless DJ's changed the GO32 licensing recently, GO32
> *can* be distributed under the GPL, which permits redistribution of a
> modified binary as long as sources are available. ]

Correct.  go32 *can* be distributed under the terms of the GPL.  My
previous statement was for cases where it's acceptable to *not* comply
with the GPL for specific binaries from specific sources.

>      I'm concerned, as it appears that I must still distribute a
> modified GO32 with OEmacs, as the DJGPP 1.11m3 doesn't work right with
> DPMI and Ctrl-Break (as the 1.11m4 update docs didn't mention anything
> about any DPMI fixes, I assume that the bug is still in 1.11m4).

Still trying to fix the Ctrl-Break bug.  DPMI problems?  What DPMI
problems?  There aren't any DPMI problems . . . ;-)

Seriously, some help fixing these bugs would be nice.  Anyone?

- Raw text -