delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1999/06/11/04:11:37

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Kevin DOT Hughes AT icl DOT com
Message-ID: <88D27A381F90D211BEE10000948332B70FF1D9@UKNORTHEX1.wg.icl.co.uk>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Gnu license
Date: Fri, 11 Jun 1999 09:03:12 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)

I hate to start this thread again, especially as it is off topic, but I am a
little concerned about a possible fiddle to software released under the gnu
license which removes the advantage of it.

As I understand it if software incorporates ANY GNU licensed code then that
software must be released under the GNU license. Now if I fiddle the source
so that it uses my internal tools in order to be built - say a special
version of the GNU compilers or a macro processor - and I NEVER release
those tools then the released source is next to useless. 

An example of this would be to encode my source and use an internal tool to
decode it prior to compilation. In this way releasing my source would not
give anything away.

I DO NOT WANT TO DO THIS, I however believe that this may happen as some
released sources cannot be used to build the binary.


Any comments much appreciated


Kevin

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019