Date: Sat, 20 Nov 2010 20:57:42 -0800 From: Charlie Kester <corky1951@comcast.net> To: freebsd-ports@freebsd.org Subject: Re: How to detect filename conflicts with uninstalled ports? Message-ID: <20101121045742.GD48679@comcast.net> In-Reply-To: <19688.41302.976685.849999@jerusalem.litteratus.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101121045742.GD48679>