#48916 closed submission (fixed)
New port: profanity
Reported by: | subpop (Link Dupont) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | ||
Port: | profanity |
Description
profanity is an ncurses, console-based XMPP client. It uses libstrophe as an XMPP library.
Attachments (3)
Change History (8)
Changed 9 years ago by subpop (Link Dupont)
Attachment: | profanity.Portfile.txt added |
---|
comment:1 Changed 7 years ago by kencu (Ken)
Changed 7 years ago by kencu (Ken)
Attachment: | config.log added |
---|
config.log showing errors with 0.5.1
comment:2 Changed 7 years ago by kencu (Ken)
passing this in
configure.args-append \ PYTHON_FRAMEWORK=${prefix}/Library/Frameworks/Python.framework
helps it find my local python (2.7). But the python installation will have to be fully specified in this port, probably to one of the 3.x versions at this point. It might be possible to do that via configure arguments, but I could not see a way to set python-config
when I looked for one. It's possible it might need to be edited directly in the makefiles with a patch.
Even when I did spec the PYTHON_FRAMEWORK
, I next encountered this error:
checking for /usr/local/opt/readline/lib... no configure: error: libreadline is required for profanity
which seems a very strange place to be looking for libreadline
, which is installed here:
/opt/local/lib/libreadline.7.0.dylib /opt/local/lib/libreadline.7.dylib /opt/local/lib/libreadline.a /opt/local/lib/libreadline.dylib
There seems to be no configure variable to specify that location to the build script, so that might need a patch as well.
Hmmm. Bogged down. No doubt fixable in the end, but it will unfortunately take some more work. I will leave this here for a while to see if it's of interest to anyone to fix this.
comment:3 Changed 7 years ago by kencu (Ken)
ah, I see. /usr/local/opt/readline/lib/
is where homebrew
would put readline
. So that must be what was expected here.
comment:4 Changed 7 years ago by kencu (Ken)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 Changed 7 years ago by kencu (Ken)
OK, Link. I sorted it out in the end. Both your submissions are now in MacPorts. I can confirm building on 10.6, 10.10, 10.11, 10.12, and 10.13. I ran it on 10.6 and 10.13 without any trouble. We'll see if the buildbots turn out any issues with the 10.7 - 10.9 group.
Haven't heard from you, and I guess that may be no surprise two years after you submitted this port -- but we're expanding manpower, and I got to it as soon as I could, being a newcomer. Hope you didn't find that too frustrating. Thanks for your submission. -- Ken
Hi Link. Thought I would work on this for you, to get 'er done. I updated the Portfile to the newest version, but ran into some kind of issue with the Python configuration:
I'll upload the Portfile I used, and the config.log.
I'm not a huge Python expert; others on MacPorts are. Perhaps you or one of them might know why this error is happening.