Date: Tue, 27 Jun 1995 11:03:14 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Cc: FreeBSD-current@FreeBSD.Org (FreeBSD current) Subject: Re: when is the supscan done? Message-ID: <199506271803.LAA07070@gndrsh.aac.dev.com> In-Reply-To: <199506271443.HAB14898@freefall.cdrom.com> from "Justin T. Gibbs" at Jun 27, 95 07:43:15 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > >Also the long list of /usr/local/bin/supscan should be converted to a > >shell function and used something like this (my shell programming > >lessons predate functions, so syntax may be wrong here). > > > > Why not something more dynamic: > > cd /home/sup > foreach i ( * ) > supscan $i /home/sup > end > > Of course thats csh not sh, but you get the idea. and leaves out the fact that there are things in /home/sup that are NOT scanable sup collections. And I sure as heck don't want the cvs-* targets to have scan files, those are done on the fly! Nope, do not do this!! Use what I wrote, correcting any syntax errors, it was not so off the cuff, but a thought out replacement that does exactly what we have now in 1/10th the lines. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506271803.LAA07070>