From owner-freebsd-ports Thu Mar 30 6: 0: 6 2000 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C9B7437B6E3 for ; Thu, 30 Mar 2000 06:00:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id GAA35337; Thu, 30 Mar 2000 06:00:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Thu, 30 Mar 2000 06:00:04 -0800 (PST) Message-Id: <200003301400.GAA35337@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Ade Lovett Subject: Re: ports/15545: New port: x11/xterm Reply-To: Ade Lovett Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/15545; it has been noted by GNATS. From: Ade Lovett To: jkoshy@FreeBSD.org Cc: naddy@mips.rhein-neckar.de, freebsd-gnats-submit@FreeBSD.org Subject: Re: ports/15545: New port: x11/xterm Date: Thu, 30 Mar 2000 07:56:35 -0600 On Thu, Mar 30, 2000 at 01:20:40AM -0800, jkoshy@FreeBSD.org wrote: > > 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 (though it will need a USE_X_PREFIX so that the app-defaults files will actually work). We already try to avoid namespace duplication and pollution with our current set of ports, this one should be no different. If the submitter (or someone else) wants to take this port and patch it so that it identifies itself as nxterm, pxterm, or whatever, and also adjust the app-defaults filenames, then it will quite happily co-exist with a regular X11 installation, and not violate POLA. -aDe -- Ade Lovett, Austin, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message