Opened 8 years ago
Closed 6 years ago
#52126 closed defect (fixed)
Remove Asterisk from Ports
| Reported by: | sshjason@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | jmroot (Joshua Root), janstary (Jan Starý) | |
| Port: | asterisk |
Description
For the last 5+ years, Asterisk has failed to install correctly on Ports. Please remove as a legitimate port.
Attachments (1)
Change History (8)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
| Milestone: | MacPorts Future |
|---|---|
| Priority: | High → Normal |
comment:2 Changed 8 years ago by mf2k (Frank Schima)
| Keywords: | has not worked for half a decade removed |
|---|---|
| Version: | 2.3.4 |
comment:3 Changed 8 years ago by neverpanic (Clemens Lang)
| Cc: | jmr@… added |
|---|
Cc'ing jmr@, who was the last to touch the port in a fashion that was possibly tested. I don't think we should keep the port in the current state, but maybe jmr@ has a different opinion and is willing to update it.
comment:4 Changed 8 years ago by jmroot (Joshua Root)
I thought #43233 was looking promising? Upstream seems to have committed a fix for the failure to compile with clang anyway: https://reviewboard.asterisk.org/r/4370/
Changed 8 years ago by kenneth.f.cunningham@…
| Attachment: | asterisk.partialfix.diff added |
|---|
asterisk 13.10.0 partial diff
comment:5 Changed 8 years ago by kenneth.f.cunningham@…
The partial fix diff updates the version to 13.10.0, downloads, configures, and builds the current version in the work directory. Install source paths are fixed, but I disabled group creation and startup item in the portfile for the moment, so I didn't fully install it. I commented out the old patches, as they didn't seem needed to build it.
I'll leave the completion of this to jmr or someone else (the OP perhaps) who knows how to tell if this is actually working correctly once installed.
Hope this helps a bit.
comment:6 Changed 8 years ago by kenneth.f.cunningham@…
I note they already changed the files, deleted 13.10.0, and updated to 13.11.0.... so the above patch refers to files that no longer exist, and therefore naturally doesn't work any more. This is kind of frustrating...wonder how often these files will come and go like that? Will update the diff to version 13.11 when I get a moment.
I did install it without adding users -- all goes well, and it at least starts up and appears to be running -- but there is some configuration to be done for this that requires some fairly specific monkeying around with config files. Not sure if you can automate this -- or if we might just move the whole config file example tree somewhere, and leave a note to the person installing to configure it according to the docs manually prior to running it.
comment:7 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | janstary added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
The Priority and Milestone fields are for use by Macports team members only.