Summary: | New port: devel/pymacs, lets you write emacs extensions in python | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | mwm | ||||
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | ||||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
mwm
2005-09-12 00:50:07 UTC
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. State Changed From-To: open->closed New port added, thank you! |