Opened 8 years ago
Closed 5 years ago
#53118 closed request (fixed)
add nccmp into macports ?
Reported by: | basmac | Owned by: | mojca (Mojca Miklavec) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch | Cc: | mojca (Mojca Miklavec) |
Port: | nccmp |
Description
Its in home-brew, so can some kind person include it into macports ? http://nccmp.sourceforge.net/#download
Attachments (1)
Change History (13)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
Keywords: | add nccmp removed |
---|---|
Version: | 2.3.5 |
comment:2 Changed 8 years ago by mojca (Mojca Miklavec)
Cc: | mojca added |
---|
comment:3 Changed 8 years ago by mojca (Mojca Miklavec)
Changed 8 years ago by mojca (Mojca Miklavec)
Attachment: | nccmp.Portfile added |
---|
comment:4 follow-up: 6 Changed 8 years ago by mojca (Mojca Miklavec)
Keywords: | haspatch added |
---|
I added a Portfile that is still missing support for reading two header files from NetCDF.
comment:5 Changed 6 years ago by Dave-Allured (Dave Allured)
I am willing to be co-maintainer. I can test and check for updates. Please update the portfile as follows. Thank you.
- version 1.8.5.0
- Release website = https://gitlab.com/remikz/nccmp/releases
- Current release source file = https://gitlab.com/remikz/nccmp/-/archive/1.8.5.0/nccmp-1.8.5.0.tar.bz2
- homepage https://gitlab.com/remikz/nccmp
- master_sites gitlab (guessing)
To get started, do not try to support the header-pad option. It is messy and may complicate the portfile. I do not think it is needed by very many people.
comment:6 Changed 6 years ago by Dave-Allured (Dave Allured)
Replying to mojca:
I added a Portfile that is still missing support for reading two header files from NetCDF.
If you avoid the header-pad option, you should not need these header files.
The purpose of reading those two header files was to export non-public symbols into nccmp, for header-pad inquiry which is not part of the normal API.
comment:7 Changed 6 years ago by mf2k (Frank Schima)
@Dave-Allured: The most helpful way to move forward is to submit a GitHub pull request with your modified Portfile.
comment:8 Changed 6 years ago by Dave-Allured (Dave Allured)
Frank, I have had some bad experiences trying to make pull requests, so I can not offer to do that. Also my experience is with code, not portfiles. All I can offer is isolated portfile suggestions when I have enough confidence in them.
Let's wait until someone else volunteers to work on this ticket.
comment:9 follow-up: 10 Changed 6 years ago by mf2k (Frank Schima)
Then you could make the modifications to Mojca's Portfile and attach that new Portfile to this ticket.
comment:10 Changed 6 years ago by Dave-Allured (Dave Allured)
I will give that a try. If you are expecting me to test the portfile before submitting, could you please point me to instructions on how to test a private version? I have never done that. Thanks.
comment:11 Changed 6 years ago by mojca (Mojca Miklavec)
I opened https://github.com/macports/macports-ports/pull/4084.
Please test if it works as expected. The maintainer doesn't need to be skilled in everything, but either attaching patches to trac or (much much better) submitting pull requests to github would be heavily desirable.
For testing please check
https://guide.macports.org/chunked/development.local-repositories.html
comment:12 Changed 5 years ago by mojca (Mojca Miklavec)
Owner: | set to mojca |
---|---|
Resolution: | → fixed |
Status: | new → closed |
It is straightforward to create a package for this, but given the current lack of manpower in MP it would be ideal if we would get at least a co-maintainer from the user base even if that user is not a computer programmer. While I can create a port for this, I don't want to spend time testing the functionality and have no idea about needs of real users. We need some volunteer who is willing to be responsible for testing, reporting when something is broken, checking for updates, ...
Are you or someone else willing to volunteer for a (co-)maintainer?