Opened 13 years ago
Closed 13 years ago
#30682 closed submission (fixed)
New port: H5Part - H5Part data storage library
Reported by: | ghweber@… | Owned by: | drkp (Dan Ports) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.2 |
Keywords: | Cc: | ghweber@… | |
Port: | H5Part |
Description
Attachments (1)
Change History (6)
Changed 13 years ago by ghweber@…
comment:1 Changed 13 years ago by drkp (Dan Ports)
Owner: | changed from macports-tickets@… to dports@… |
---|---|
Port: | H5Part added |
Status: | new → assigned |
Version: | 2.0.1 → 2.0.2 |
comment:2 Changed 13 years ago by drkp (Dan Ports)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 Changed 13 years ago by ghweber@…
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Updating to 1.6.6 certainly makes sense. I am happy to update the portfile (if I can do that myself).
comment:5 Changed 13 years ago by drkp (Dan Ports)
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
It's best to file that as a separate ticket with a unified diff of the Portfile. Including haspatch maintainer
in the keywords field should help make sure that it gets applied quickly. (That's not required, but it indicates that there's a patch is ready to be applied and I periodically scan for tickets tagged that way.)
Note: See
TracTickets for help on using
tickets.
Thanks, committed in r90915 -- sorry for the delay. I changed the hardcoded /opt/local to ${prefix} and made a couple other minor changes (license, checksum types).
I see that 1.6.6 is now available; should we update the portfile?