Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!samsung!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!vjs@rhyolite.wpd.sgi.com From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver) Newsgroups: comp.sys.sgi Subject: Re: RCS question Message-ID: <85549@sgi.sgi.com> Date: 14 Feb 91 22:12:27 GMT References: <9102110954.AA05236@tdisys.uucp> Sender: guest@sgi.sgi.com Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 21 In article <9102110954.AA05236@tdisys.uucp>, mogenix@tdisys.UUCP (MOGENET) writes: > From: "Emmanuel Mogenet" > Subject: > > I'd like to add a few questions: > ... > 2. As RCS is a GNU software, what juridical maze allowed > SGI not to provide the sources ? > ... The RCS in IRIX 3.3.2 predates the GNU involvement with people at Purdue. It predates the source on the 4.3BSD tapes. It many even predate the founding of Stallman's FSF--I don't remember the important dates. SGI is not violating the copyleft, and in fact one of the difficulties that Paul is working on is how to comply with the copyleft when his new version is shipped. The easy issues already solved include releasing source for our enhancements of the old RCS to support symbolic links for archives. The hard issues including finding space on some tape for the new RCS source. Vernon Schryver, vjs@sgi.com