From owner-freebsd-ports Wed Mar 29 15: 6: 7 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 B508C37B7F1; Wed, 29 Mar 2000 14:23:20 -0800 (PST) (envelope-from ade@FreeBSD.org) Received: (from ade@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA62449; Wed, 29 Mar 2000 14:23:20 -0800 (PST) (envelope-from ade@FreeBSD.org) Date: Wed, 29 Mar 2000 14:23:20 -0800 (PST) From: Message-Id: <200003292223.OAA62449@freefall.freebsd.org> To: naddy@mips.rhein-neckar.de, ade@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: ports/15545: New port: x11/xterm Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: New port: x11/xterm State-Changed-From-To: open->feedback State-Changed-By: ade State-Changed-When: Wed Mar 29 14:19:26 PST 2000 State-Changed-Why: Has the functionality in this port been rolled into either XFree86 3.3.6 or one of the pre-4.0 snapshots? This port worries me in that it overwrites a couple of standard X11 binaries (xterm and resize), so that a pkg_delete would result in _no_ xterm being available, which is a bad thing. Unless a solution can be found to this problem (remember to deal with the app-defaults too), I believe that this submission should just die peacefully. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message