From owner-freebsd-ports@FreeBSD.ORG Sun Nov 21 04:58:01 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B5661065670 for ; Sun, 21 Nov 2010 04:58:01 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id E8CC38FC08 for ; Sun, 21 Nov 2010 04:58:00 +0000 (UTC) Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta05.westchester.pa.mail.comcast.net with comcast id Zgvi1f0031uE5Es55gy1oM; Sun, 21 Nov 2010 04:58:01 +0000 Received: from comcast.net ([98.203.142.76]) by omta16.westchester.pa.mail.comcast.net with comcast id Zgxz1f0011f6R9u3cgxz49; Sun, 21 Nov 2010 04:58:01 +0000 Received: by comcast.net (sSMTP sendmail emulation); Sat, 20 Nov 2010 20:57:42 -0800 Date: Sat, 20 Nov 2010 20:57:42 -0800 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20101121045742.GD48679@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <20101121012336.GM13998@comcast.net> <20101121032306.GB48679@comcast.net> <19688.37613.144903.851371@jerusalem.litteratus.org> <20101121040511.GC48679@comcast.net> <19688.41302.976685.849999@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <19688.41302.976685.849999@jerusalem.litteratus.org> X-Mailer: Mutt 1.5.20 X-Composer: Vim 7.2 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: How to detect filename conflicts with uninstalled ports? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2010 04:58:01 -0000 On Sat 20 Nov 2010 at 20:34:30 PST Robert Huff wrote: > >Charlie Kester writes: > >> 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. > > If this is a one-time thing, your best policy might be to >provide the (proposed) name and see if anyone raises a red flag. Two names, actually: "box" and "boxer". I'm amazed these names don't seem to be taken. I remember boxer as the name of an editor on another platform, but it was never ported to BSD. There's "boxes" which is a little utility for formatting comment blocks and similar text. But no "box". Weird. Anyway, the "box" I have in mind is a programming language for graphics. http://boxc.sourceforge.net. Boxer is the name of its Python-based GUI. I have the portfiles ready to submit, assuming my tinderbox run goes OK. This query was one of my final sanity checks.