How to detect filename conflicts with uninstalled ports?

[Charlie Kester]

On Sat 20 Nov 2010 at 19:33:01 PST Robert Huff wrote:
>
>Charlie Kester writes:
>
>>  On Sat 20 Nov 2010 at 17:23:37 PST Charlie Kester wrote:
>>  >I'm working on a new port that installs a program with a name that seems
>>  >like it would already be taken, but I don't have anything by that name
>>  >on my system -- even though I have lots of ports installed.
>>  >
>>  >I know that I can use "portsdb -r" to find all the ports that depend on
>>  >a given port, whether they're installed or not.  Is there a similar way
>>  >to determine if an uninstalled port installs a file with a given name?
>>
>>  As someone kindly reminded me, "find" and "grep" are my friends:
>>
>>  $ cd /usr/ports
>>  $ find . -name "pkg-plist" -exec grep -H "bin/progname" {} \;
>>  $ find . -name Makefile -exec grep -H "bin/progname" {} \;
>
>	The former accounts for static packing lists; does the second
>do the same for dynamic packing lists?

Probably not.  I was just thinking of ports that define PLIST_FILES in
their Makefiles, in lieu of a pkg-plist.

But I expect these two find & greps will detect the majority of filename
conflicts.  Unless someone has a better recommendation, I'll settle for
less than perfect.

Besides, the Porter's Handbook strongly discourages the use of dynamic
package lists (although it does not forbid them).  So if I'm not aware
of a conflict with someone else's port that uses them anyway, I figure
it's as much their fault as mine.  ;)