Article View: comp.os.msdos.programmer
Article #5203Re: Getting RCS to work
From: Greg Wettstein
Date: Thu, 14 Mar 1991 15:14
Date: Thu, 14 Mar 1991 15:14
67 lines
3649 bytes
3649 bytes
> In article <1991Mar7.041215.19021@twinsun.com> eggert@twinsun.com (Paul
Eggert) write
> >john@hpnmdla.hp.com (John McLaughlin) writes:
> >
> >>A while back I asked a question regarding a SCCS or RCS package
> >>available in the public domain that works...
> >
> >Legal note: RCS is copyrighted, and is not in the public domain.
> >However, recent versions of RCS have been placed under the GNU ``copyleft'',
> >a license that lets you freely distribute RCS executables
> >if you also distribute their source.
> >This is all described in the file COPYING that comes with the RCS
distribution;
> >if your copy of RCS lacks COPYING, please write to gnu@prep.ai.mit.edu.
>
> The copy of RCS that I got off of simtel didn't have the source but I was able
> to get the source from another location. I didn't fully read the copying
file.
>
> Has anyone ported RCS to the Borland line of compilers? If anyone has could
> you please point me to the source? I would like the DOS version to save the
> log files with the .?_v extension so I can make the dependency statement in
> the makefile.
>
> Thanks in advance.
>
> Gary Krone
> gkrone@bbs.naitc.com
We have just completed porting RCS 5.5 to MS-DOS using MSC 6.00A and the
virgin sources as obtained from prep.ai.mit.edu. The resultant product
passes the rcstest.sh script which is bundled with the 5.5 product.
I have tried to maintain a product which is as consistent with the UNIX(c)
product as possible. Since commas(,) are not legal in MS-DOS filenames we
opted to use the apostrophe(') as the RCS archive designator. This of
course poses the unfortunate limitation of single character filename
extensions.
The binaries are packaged and ready to be delivered to Mr. Davidsen and
of course ultimately to comp.sys.ibm.pc.binaries. I sent a copy of the
patches to a fine gentleman up in Canada who expressed an interest in the
project and I am waiting for him to confirm that the binaries perform in
his environment as well as mine.
One of our mutual ambitions (The Canadian group and mine) is to provide
the community with an RCS port whose stability is not in any type of
question. This has resulted in delaying the release of the package but
a delay which will hopefully be of benefit to everyone ultimately involved
with the binaries.
I will post a short notice to this group and the pc binaries discussion group
when the package gets shipped. If anyone would like to converse about the
distribution please use the e-mail address in my sig as this will insure that
communications get routed directly to my office.
As always,
Dr. G.W. Wettstein
Oncology Research Division Computing Facility
Fargo Clinic / MeritCare
UUCP: uunet!plains!wind!greg
INTERNET: greg%wind.uucp@plains.nodak.edu
Phone: 7001-234-2833
`The truest mark of a man's wisdom is his ability to listen to other
men expound their wisdom.'
Technical Details
Message-ID:
<91073.091431NU013809@NDSUVM1.BITNET>Path:
arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!cs.utexas.edu!samsung!emory!gatech!psuvax1!psuvm!cunyvm!ndsuvm1!nu013809References:
<11270006@hpnmdla.hp.com> <1991Mar7.041215.19021@twinsun.com> <1991Mar11.192222.22681@pcserver2.naitc.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!cs.utexas.edu!samsung!emory!gatech!psuvax1!psuvm!cunyvm!ndsuvm1!nu013809 From: NU013809@NDSUVM1.BITNET (Greg Wettstein) Newsgroups: comp.os.msdos.programmer Subject: Re: Getting RCS to work Message-ID: <91073.091431NU013809@NDSUVM1.BITNET> Date: 14 Mar 91 15:14:31 GMT References: <11270006@hpnmdla.hp.com> <1991Mar7.041215.19021@twinsun.com> <1991Mar11.192222.22681@pcserver2.naitc.com> Organization: North Dakota Higher Education Computer Network Lines: 67