[MacPorts] #54035: Become maintainer of and update port 'ncview'

[MacPorts]

#54035: Become maintainer of and update port 'ncview'
---------------------------+------------------------
  Reporter:  thiagoveloso  |      Owner:  seanfarley
      Type:  submission    |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.4.1
Resolution:  fixed         |   Keywords:
      Port:  ncview        |
---------------------------+------------------------

Comment (by seanfarley):

 Replying to [comment:4 thiagoveloso]:
 > Replying to [comment:3 seanfarley]:
 > > Well, try to get something together and I can review it.
 >
 > Ok, I've attached a tentative Portfile. What still needs to be fixed:
 >
 > - not sure what revision it is

 That gets reset every time the version is updated. The revision is usually
 for 'revbumping': when a port needs to be updated due to a dependency
 changing.

 > - I would still like to be the maintainer of this port :D

 Sure, sounds good. I added 'openmaintainer' as well so others can help
 out.

 > - I don't know how to point out the download address to the latest
 source code: ftp://cirrus.ucsd.edu/pub/ncview/ncview-2.1.7.tar.gz

 If you change the version, then it will automatically download this file
 since `master_sites` already points to `ftp://cirrus.ucsd.edu/pub/ncview/`

 > - checksums should be changed accordingly

 I use `sudo port -v upgrade PORT` which will print the new checksums.

 > - required libpng provides library libpng.dylib, but ncview requires
 libpng.so. The solution for me is to create a symbolic link, but I don't
 know how to to that on the Portfile: sudo ln -s
 /opt/local/lib/libpng.dylib /opt/local/lib/libpng.so

 The patchfile `patch-configure.diff` had most of these changes. Just
 `udunits2` needed to added (same pattern as in the previous patchfile,
 though).

 > - I am not sure if anything below the "configure.args" section is
 actually required (when building ncview manually I don't need any of it)

 If you're building manually, be careful to check the environment variables
 being used. These `configure.args` are needed so that only `${prefix}` is
 searched and linked against in MacPorts.

 > Is any of this helpful to you?

 Yep :-) I was able to update the port. You're now the maintainer,
 congrats!

--
Ticket URL: <https://trac.macports.org/ticket/54035#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS