From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Sep 12 07:10:18 2005 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B9BA16A41F for ; Mon, 12 Sep 2005 07:10:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34FC943D45 for ; Mon, 12 Sep 2005 07:10:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8C7AIEr099591 for ; Mon, 12 Sep 2005 07:10:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8C7AHIb099590; Mon, 12 Sep 2005 07:10:17 GMT (envelope-from gnats) Date: Mon, 12 Sep 2005 07:10:17 GMT Message-Id: <200509120710.j8C7AHIb099590@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: mwm@mired.org Cc: Subject: Re: ports/85995: New port: devel/pymacs, lets you write emacs extensions in python X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mwm@mired.org List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 07:10:18 -0000 The following reply was made to PR ports/85995; it has been noted by GNATS. From: mwm@mired.org To: bug-followup@FreeBSD.org, mwm@mired.org Cc: Subject: Re: ports/85995: New port: devel/pymacs, lets you write emacs extensions in python Date: 12 Sep 2005 07:09:53 -0000 I should have mentioned this in the original posting, but did things in a bit of a hurry. My bad. There is a bug in the xemacs21 port (actually, in the emacs ports in general) that causes this port to fail to install if you set EMACS_PORT_NAME to xemacs21. You can work around this bug by setting EMACS_PORT_NAME to another emacs - or so I've been led to believe. I haven't tested any of them, for rather convoluted reasons. In retrospect, making that the default EMACS_PORT_NAME xemacs21 probably wasn't such a good idea. It won't matter much - the only people liable to install this port should already have an emacs installed. If it's not xemacs21, they'll set EMACS_PORT_NAME appropriately, and everything should work. If it is xemacs21 - well, they can't install another emacs because they conflict. So they can't install the port in any case. Anyway, the bug in question is ports/37596. The person assigned to the bug - sem - has a fix for it. I have a copy of that patch, which is how I tested this port with xemacs21 installed. The patch is waiting on a full build cycle on pointyhat, which will happen after 6.0-RELEASE.