Return to BSD News archive
Xref: sserve comp.os.386bsd.development:522 comp.os.linux:35433 Newsgroups: comp.os.386bsd.development,comp.os.linux Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!ira.uka.de!math.fu-berlin.de!easix!exnet2!exnet!dcs.ed.ac.uk!sct From: sct@dcs.ed.ac.uk (Stephen Tweedie) Subject: Re: PLEA across the board. In-Reply-To: peter@NeoSoft.com's message of 21 Apr 93 01:51:27 GMT Message-ID: <SCT.93Apr21213242@damsay.dcs.ed.ac.uk> Sender: cnews@dcs.ed.ac.uk (UseNet News Admin) Organization: University of Edinburgh Dept. of Computer Science, Scotland References: <jmonroyC5rz7x.LA1@netcom.com> <C5t95t.Ft3@sugar.neosoft.com> Date: Wed, 21 Apr 1993 21:32:42 GMT Lines: 23 In article <C5t95t.Ft3@sugar.neosoft.com>, peter@NeoSoft.com (Peter da Silva) writes: > Put a string in that can be grepped for with "what". Right now, the > output from "what" is a little verbose (it gives you the version > number of every module in the file), but a "what -q" that just gives > strings flagged with a "program version number" would be a trivial > enhancement, then you could do "what /bin/*" and see what version of > *everything* you're using. > Much better than adding an option (that might conflict with existing > options) to every program. Why not just do it the RCS way, and have a "$Id:$" string in any modules you want to identify. This way, the information is automatically kept uptodate by RCS or CVS, and you can use the existing "ident" command from RCS to identify both source and code (assuming you have $Id$ string constants in your modules). Cheers, Stephen Tweedie. --- Stephen Tweedie <sct@uk.ac.ed.dcs> (Internet: <sct@dcs.ed.ac.uk>) Department of Computer Science, Edinburgh University, Scotland.