Date: Sat, 1 Apr 2000 03:49:31 +0200 From: Christian Weisgerber <naddy@mips.rhein-neckar.de> To: Will Andrews <andrews@technologist.com> Cc: freebsd-ports@FreeBSD.ORG Subject: Re: ports/15545: New port: x11/xterm Message-ID: <20000401034931.C581@bigeye.rhein-neckar.de> In-Reply-To: <20000331191740.C1615@argon.blackdawn.com>; from andrews@technologist.com on Fri, Mar 31, 2000 at 07:17:40PM -0500 References: <200003300200.SAA03085@freefall.freebsd.org> <200003300920.BAA47089@freefall.freebsd.org> <20000330075635.I312@supernews.com> <20000401013841.B581@bigeye.rhein-neckar.de> <20000331191740.C1615@argon.blackdawn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Will Andrews:
> > nxterm has been abused by Red Hat for different flavors of xterm.
> > Thomas Dickey suggests xfree86-xterm, which is however both clumsy
> > and counter-intuitive.
>
> xterm-devel or some other suffix.
Note that we aren't talking about the name of the port but of the
installed executable. And once the port is installed we want people
to use this version of xterm in preference to the one in ${X11BASE}/bin.
We do have quite a few cases where ports conflict and install
binaries by the same name, e.g. lynx{,-ssl,-current}, or the four
w3m incarnations.
--
Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000401034931.C581>