#37617 closed submission (fixed)
ghsum @0.1.0 submission
| Reported by: | rod@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.2 |
| Keywords: | Cc: | cooljeanius (Eric Gallager) | |
| Port: | ghsum |
Description
attached Portfile for new port 'ghsum'
Attachments (1)
Change History (7)
Changed 11 years ago by rod@…
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to ryandesign@… |
|---|---|
| Status: | new → assigned |
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Added in r101572 with these changes:
- fixed capitalization of GitHub and MacPorts in descriptions
- minor reformatting
- fixed fetch: changed version from 0.0.1 to 0.1.0
- fixed destroot: there is no file LICENSE in your source distribution, so changed LICENSE to README.md
Please be sure to test your portfiles before you submit them.
Note that for the purpose of MacPorts, this utility is not needed. To update a port, you edit the version line and save the file, then run sudo port -d checksum. MacPorts will fetch the new distfile, then print a message that the checksums don't match, along with what the new checksums are.
I usually automate the process of updating a port using my portcheckup script.
comment:3 Changed 11 years ago by rod@…
Ah right - ok thanks that's good to know. I didn't want to re-invent the wheel here, but my google-fu was clearly not up to finding out about these tools.
I've been having a bit of trouble developing and updating portfiles, and hacking up some tools to help. So if there's any information you can point me to (outside of the guide of course I've read that) that would be really helpful.
I'll try those tools you linked, and I assume they'll solve this problem - so is there a way to remove this port now? Or will it always need to be a part of Macports?
comment:4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
We can of course remove it if you'd like. I recommend you write to the macports-dev mailing list and ask any portfile development questions you have there, that way other maintainers can give you their tips and tricks.
comment:5 Changed 11 years ago by cooljeanius (Eric Gallager)
I say keep it. It's not hurting anything by staying, except maybe causing some confusion. I'm a fan of the Perl motto that There's more than one way to do it, and I'd say that as long as users are aware that this is the case with this port, they should be fine.
Thanks.