a563@mindlink.UUCP (Dave Kirsch) (08/17/90)
> lfk@athena.mit.edu writes: > The documentation requires troff. If desired by many, I can post the > postscript code for the documentation. Just a small question, where can I get troff (with some documentation). I have gotten troff files before, and had nothing I could "run" them through to get some readable text (and reading troff files isn't fun). So, where can I get a TROFF.EXE for MS-DOS? -- -- David Kirsch UUCP: {uunet,ubc-cs}!van-bc!rsoft!mindlink!a563 Voice: (604) 327-4404 a563@mindlink.UUCP Vancouver, British Columbia 'In-no-sense? Nonsense!' - The Art Of Noise
lfk@athena.mit.edu (Lee F Kolakowski) (08/18/90)
As you may have noticed, a port of GNURCS (RCS 4.0) has been posted on
cpib. The sources are also on the way. There is a small file, that
follows, that *I* left out of the distribution.
I am willing to maintain any code cleanups, enhancements etc.
--------snip----here------------
This is a small note to go with the MS-DOS ports of RCS (Revsion
Control System).
These sources were originally obtained from a posting on
fj.binaries.msdos (a Japanese domain newsgroup) and the olny
documentation associated with the port was in Kanji.
I'd like to give more credit to the original port, but....
These sources can with binaries that are present in the DOSRCSex.zoo
archive which has been uuencoded and split into several parts with uue
These are not modified or recompiled by me and appear to be compiled by
MSC version 5 or 5.1.
I took these sources and went back towards the Unix code a little
adding support for names with '/' as the path separator, and support
for the MKS shells command line parsing. Only one program enclosed
in the MKS_bin requires the MKS toolkit and that is rcsmerge.
All of the RCS commands need access to a diff in the path. GNU diff
and MKS work with the MKS versions. The DOS_bin versions are wired to
use a -a command switch for GNU diff.
The Documentation and the source is in DOSRCSs.ua{...}
The MKS binaries and shell scripts are in MKSRCSex.ua{...}
The Original DOS binaries are in DOSRCSex.ua{...}
The documentation requires troff. If desired by many, I can post the
postscript code for the documentation.
I am willing to maintain this code for a while
so, mail and bugs to me at lfk@athena.mit.edu
There are so many parts to this, I have also placed it as a complete
compressed tar file in mbio.med.upenn.edu (128.91.18.14) for a while.
-Frank
--
Frank Kolakowski
======================================================================
|lfk@athena.mit.edu || Lee F. Kolakowski |
|lfk@eastman2.mit.edu || M.I.T. |
|kolakowski@wccf.mit.edu || Dept of Chemistry |
|lfk@mbio.med.upenn.edu || Room 18-506 |
|lfk@hx.lcs.mit.edu || 77 Massachusetts Ave.|
|AT&T: 1-617-253-1866 || Cambridge, MA 02139 |
|--------------------------------------------------------------------|
| #include <woes.h> |
| One-Liner Here! |
======================================================================lfk@athena.mit.edu (Lee F Kolakowski) (08/18/90)
On 17 Aug 90 05:58:56 GMT, a563@mindlink.UUCP (Dave Kirsch) said: >> lfk@athena.mit.edu writes: >> The documentation requires troff. If desired by many, I can post the >> postscript code for the documentation. > Just a small question, where can I get troff (with some documentation). I have > gotten troff files before, and had nothing I could "run" them through to get > some readable text (and reading troff files isn't fun). You have a couple of choices: 1) Get an account on a unix system that has DWB 2.0 (this has pic generated stuff in it). 2) Get the Groff distribution (written in G++, needs gcc...) 3) By a Ditroff for your platform (MSDOS versions are sold by Elan and MKS (Softquad Product). -- Frank Kolakowski ====================================================================== |lfk@athena.mit.edu || Lee F. Kolakowski | |lfk@eastman2.mit.edu || M.I.T. | |kolakowski@wccf.mit.edu || Dept of Chemistry | |lfk@mbio.med.upenn.edu || Room 18-506 | |lfk@hx.lcs.mit.edu || 77 Massachusetts Ave.| |AT&T: 1-617-253-1866 || Cambridge, MA 02139 | |--------------------------------------------------------------------| | #include <woes.h> | | One-Liner Here! | ======================================================================
richw@hplsla.HP.COM (Rich Wilson) (08/21/90)
/ hplsla:comp.binaries.ibm.pc.d / lfk@athena.mit.edu (Lee F Kolakowski) / 11:38 am Aug 17, 1990 / There are so many parts to this, I have also placed it as a complete compressed tar file in mbio.med.upenn.edu (128.91.18.14) for a while. -Frank --------------------- I played around with this last night, and can offer a couple pointers: The compressed tar file above should probably be uncompressed before you move it to your PC, since the MKS uncompress can't handle its 16-bit conpressed format. The un-taring can be done by MKS. This DOS version stores rcs files in like-named files in an 'rcs' subdirectory. (no ,v stuff is used). I had problems (at least with the MKS binaries) if I didn't have the environment variable LOGNAME defined. Doing a 'ci', I ended up with an author name of '(null)' in the rcs file, and subsequent operations on the file resulted in error messages. Defining LOGNAME helped. Now for the questions: Can anyone show how to integrate this with Borland make? Will the make I just saw posted integrate with RCS any better? My desire would be that the make process would, (for example if you were making the file t.c) look first for t.c and check for t.obj being up to date; if t.c was not present, it should check for rcs/t.c, and if t.obj was out of date with respect to it, would do a co, cc, rm sequence. Rich Wilson
ccoprrm@prism.gatech.EDU (Robert E. Minsk) (09/11/90)
I missed the posting of DOSRCS binaries and would like to obtain them. I
have ftp access!! I have the source but don't have msc.
Thanks,
Robert Minsk
Robert E. Minsk - Information Technology | Save the whales... |
ARPA: ccoprrm@prism.gatech.edu | Collect the whole set |
uucp: ...!{allegra,amd,hplabs,seismo,ut-ngp}!gatech!prism!ccoprrm
Georgia Institute of Technology, Atlanta Georgia, 30332 berg@cip-s04.informatik.rwth-aachen.de (AKA Solitair) (09/11/90)
While installing it I noticed that the programs look for "diff" in the
current directory. Did I miss something, or do they really do this.
I glanced (time is in short supply :-) at the sources and noticed
this might be caused by NOT using an execp (notice the p) instead of
an exec call; I thought MSDOS does not automatically search the PATH,
this has to be done explicitly in the library (hence the execp).
Can anybody confirm this?
--
Sincerely, berg%cip-s01.informatik.rwth-aachen.de@unido.bitnet
Stephen R. van den Berg.
"I code it in 5 min, optimize it in 90 min, because it's so well optimized:
it runs in only 5 min. Actually, most of the time I optimize programs."