From owner-freebsd-ports Fri Mar 31 15:57:38 2000 Delivered-To: freebsd-ports@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 4AC5937C312; Fri, 31 Mar 2000 15:57:21 -0800 (PST) (envelope-from naddy@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id BAA22078; Sat, 1 Apr 2000 01:57:18 +0200 (CEST) (envelope-from naddy@bigeye.rhein-neckar.de) Received: (from naddy@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id BAA61801; Sat, 1 Apr 2000 01:38:41 +0200 (CEST) (envelope-from naddy) Date: Sat, 1 Apr 2000 01:38:41 +0200 From: Christian Weisgerber To: Ade Lovett Cc: freebsd-ports@FreeBSD.org Subject: Re: ports/15545: New port: x11/xterm Message-ID: <20000401013841.B581@bigeye.rhein-neckar.de> References: <200003300200.SAA03085@freefall.freebsd.org> <200003300920.BAA47089@freefall.freebsd.org> <20000330075635.I312@supernews.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000330075635.I312@supernews.com>; from ade@FreeBSD.org on Thu, Mar 30, 2000 at 07:56:35AM -0600 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ade Lovett: > > Why not have the port rename the executable and app-default file to > > something else? (nxterm? xterm-the-next-generation :)?) and allow both > > flavours to coexist? > > Precisely. If it does this, then all my objections go away If this was your point all along, you could have said so directly. :-/ > If the submitter (or someone else) wants to take this port and > patch it so that it identifies itself as nxterm, pxterm, or > whatever, Suggestions? 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. -- 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