#25027 closed submission (fixed)
octave-communications Portfile
| Reported by: | iamstuffed@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.2 |
| Keywords: | Cc: | ||
| Port: | octave-communications |
Description
This is a Portfile for the octave-communications package. I just copied another octave package Portfile and changed the info to reflect this package, and it seemed to work.
Attachments (1)
Change History (10)
Changed 14 years ago by iamstuffed@…
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to ryandesign@… |
|---|---|
| Port: | octave-communications added |
| Status: | new → assigned |
comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I committed it in r68063 with these changes
- fixed the trailing whitespace pointed out by
port lint --nitpick - fixed the quoting in the livecheck.regex; the backslashes either needed to have been doubled (which looks messy and I prefer to avoid it if possible), or, since this livecheck.regex doesn't need variable interpolation, I changed it to a curly-bracket-quoted string instead
- turned off the universal variant since it didn't build anything universal
- a few other minor formatting changes
comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Hm, now that I actually test the livecheck (which I should have done before), the URL it's checking is returning an error. If there's a new page it should be checking instead, please let me know.
comment:4 Changed 14 years ago by iamstuffed@…
I'm not sure, since I'm no pro at Portfiles. It installed perfectly fine though the way it was.
comment:5 Changed 14 years ago by iamstuffed@…
Whoops. Forgot to add, I installed it earlier today on a Snow Leopard machine, if that matters.
comment:6 follow-up: 8 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
It installed fine for me too. Livecheck is not used during the installation process, but by port maintainers to check whether the port needs to be updated. You can read about this feature in the guide if you're interested.
I found the new URL and will be updating all affected octave ports in a moment.
comment:7 Changed 14 years ago by iamstuffed@…
I didn't know how to specify it, but this package requires that the octave-signals package be installed also. None of the other octave packages had any dependencies listed, other than Octave, so I didn't have an example on how to do it.
See here: http://octave.sourceforge.net/communications/index.html
comment:8 follow-up: 9 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ryandesign@…:
I found the new URL and will be updating all affected octave ports in a moment.
I'll handle this in #25035.
Replying to iamstuffed@…:
I didn't know how to specify it, but this package requires that the octave-signals package be installed also. None of the other octave packages had any dependencies listed, other than Octave, so I didn't have an example on how to do it.
Thanks for mentioning this. As an example, you could look at octave-ga, which has a dependency octave-miscellaneous. You simply add it to the depends_lib line. I fixed this in r68069.
comment:9 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ryandesign@…:
octave-ga [...] has a dependency octave-miscellaneous.
Actually octave-ga is apparently supposed to have a dependency on octave-communications; see #22777. The octave-forge page doesn't mention anything about octave-miscellaneous. I wonder if that means we should remove octave-ga's dependency on octave-miscellaneous. I guess that would be a matter to file in another ticket.
Thanks!