From owner-freebsd-ports  Wed Dec 18 15:44:51 1996
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA10330
          for ports-outgoing; Wed, 18 Dec 1996 15:44:51 -0800 (PST)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA10325
          for <ports@freebsd.org>; Wed, 18 Dec 1996 15:44:49 -0800 (PST)
Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id PAA03800; Wed, 18 Dec 1996 15:44:37 -0800 (PST)
Date: Wed, 18 Dec 1996 15:44:37 -0800 (PST)
Message-Id: <199612182344.PAA03800@vader.cs.berkeley.edu>
To: fenner@parc.xerox.com
CC: fenner@parc.xerox.com, msmith@atrad.adelaide.edu.au, ports@freebsd.org
In-reply-to: <96Dec18.085846pst.177712@crevenia.parc.xerox.com> (message from Bill Fenner on Wed, 18 Dec 1996 08:58:37 PST)
Subject: Re: Ports tidy-up sweep
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * >Unfortunately, this doesn't work, as we now have "/" in the file path
 * >substituted there.
 * 
 * Oh, I was just copying Mike's grep suggestion.  My suggestion is really
 * just to get rid of the grep; if you're happy with "grep $$file" then
 * awk "/$$file/" is just as good.

What I tried to say is that the "$$file" part may be substituted with
something with a "/" in it, in which case awk will get confused, but
grep won't (/ is not a special character to grep).

Try it on (say) ports/print/xdvi, and you'll see what I mean.

Satoshi