delorie.com/archives/browse.cgi | search |
Date: | Wed, 19 Mar 1997 04:47:18 -0500 (EST) |
From: | "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca> |
Reply-To: | "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca> |
To: | jdashiel AT eagle1 DOT eaglenet DOT com |
cc: | "Alaric B. Williams" <alaric AT abwillms DOT demon DOT co DOT uk>, |
Dennis Janssen <nessnaj AT worldonline DOT nl>, | |
OpenDOS Mailing List <opendos AT mail DOT tacoma DOT net> | |
Subject: | Re: [opendos] Sources |
In-Reply-To: | <Pine.NXT.3.95.970315144038.8829G-100000@eagle1> |
Message-ID: | <Pine.LNX.3.95.970319044028.12128E-100000@capslock.com> |
Organization: | Total disorganization. |
MIME-Version: | 1.0 |
On Sat, 15 Mar 1997 jdashiel AT eagle1 DOT eaglenet DOT com wrote: > There's an easy way to solve that problem permanently. > First pop all the sources out and use rcs to put all of them > into the next system. I believe rcs is covered by the g.p.l. and > it has been known to save programmer's bacon in the past too. Yes, but that would require rcs being installed on the particular person's computer who wants to analyse the source code. Since many people will be downloading the sources and editing them to their hearts content, the SCS would be useless because many people would have the sources. Therefore *ANY* SCS is practically useless. The best way to release the sources will be in a standard ZIP or TGZ archive (probably ZIP). The archive will decompress into the source tree which can be built with "make". That way one only needs to have the "make" program, and the proper C compiler. For example: 1) Download source archive. 2) Unzip archive. 3) CD into the dir that you unzipped it into. 4) type "make" Then all you need is the proper C compiler that was used. This will probably be Borland C++ 3.1 or Micro C or some other 16 bit compiler. The sources will also probably be ported to DJGPP as well. (The utilities and COMMAND.COM anyways.) Any SCS will just complicate the whole mess. I believe that Gene is porting the code to a single C compiler, and extracting sources from the SCS that was used and writing makefiles anyways. TTYL Mike A. Harris | http://blackwidow.saultc.on.ca/~mharris Computer Consultant | Coming soon: dynamic-IP-freedom... My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html mailto:mharris AT blackwidow DOT saultc DOT on DOT ca
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |