Bug 85995 - New port: devel/pymacs, lets you write emacs extensions in python
Summary: New port: devel/pymacs, lets you write emacs extensions in python
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-12 00:50 UTC by mwm
Modified: 2005-09-12 08:29 UTC (History)
0 users

See Also:


Attachments
file.shar (3.67 KB, text/plain)
2005-09-12 00:50 UTC, mwm
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description mwm 2005-09-12 00:50:07 UTC
You have to write emacs extensions in lisp. Unless you have pymacs
installed, anyway. Current versions of at least one other ports
software (devel/bicyclerepair) now depend on pymacs.

Fix: Commit the attached port.
How-To-Repeat: 
Try writing them in something else! Or try installing the latest
version of the bicyclerepair software for use with emacs.
Comment 1 mwm 2005-09-12 08:09:53 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.
Comment 2 Pav Lucistnik freebsd_committer freebsd_triage 2005-09-12 08:29:31 UTC
State Changed
From-To: open->closed

New port added, thank you!