Newer (beta- or pre-release) packages are often available for intrepid Debian/Ubuntu users as described <ahref="https://github.com/nco/nco/tree/master/doc/beta.txt">here</a>.
<dt>Debian package for most recent NCO release (install with, e.g., ‘<tt>dpkg --install nco_4.7.9-1_i386.deb</tt>’):</dt>
cd ~/bin;tar cvzf ${DATA}/nco-4.7.9.macosx.10.14.tar.gz nc*;scp ${DATA}/nco-4.7.9.macosx.10.14.tar.gz zender,nco@web.sf.net:/home/project-web/nco/htdocs/src
cd ~/bin;tar cvzf ${DATA}/nco-4.8.0.macosx.10.14.tar.gz nc*;scp ${DATA}/nco-4.8.0.macosx.10.14.tar.gz zender,nco@web.sf.net:/home/project-web/nco/htdocs/src
-->
The most up-to-date executables are probably those in the tarball below. Those unfamiliar with installing executables from tarballs may try the (older) <ahref="http://en.wikipedia.org/wiki/Apple_Disk_Image">DMG</a> files (you may need to add <tt>/opt/local/bin</tt> to your executable path to access those operators).
the <ahref="http://trac.macosforge.org/projects/macports/wiki">MacPorts</a>
<ahref="#bld_macports">dependencies</a> for <ahref="http://svn.macports.org/repository/macports/trunk/dports/science/nco">NCO</a>). Maintained by NCO Project.</li>
...
...
@@ -904,9 +917,9 @@ To build NCO from source yourself using MSVC with CMake, please see example in <
<li><ahref="src/nco-4.7.9.windows.mvs.exe">nco-4.7.9.windows.mvs.exe</a> (<!--#fsize file="src/nco-4.7.9.windows.mvs.exe"-->) : Windows Self-Extracting Installer (last updated <!--#flastmod file="src/nco-4.7.9.windows.mvs.exe"-->). Maintained by Pedro Vicente.</li>
<li><ahref="src/nco-4.8.0.windows.mvs.exe">nco-4.8.0.windows.mvs.exe</a> (<!--#fsize file="src/nco-4.8.0.windows.mvs.exe"-->) : Windows Self-Extracting Installer (last updated <!--#flastmod file="src/nco-4.8.0.windows.mvs.exe"-->). Maintained by Pedro Vicente.</li>
These commands retrieve the current (“bleeding edge”)
development version of NCO into a local directory named <tt>nco</tt>:
<p><tt>git clone https://github.com/nco/nco.git ~/nco</tt></p> or
...
...
@@ -1109,9 +1122,9 @@ development version of NCO into a local directory named <tt>nco</tt>:
Track changes to the development version using
<p><tt>cd nco;git pull</tt></p>
One difference between running a "tagged" release
(e.g., <tt>4.7.9</tt>) and the development version is that the
(e.g., <tt>4.8.0</tt>) and the development version is that the
tagged release operators will print a valid version number (e.g.,
<tt>4.7.9</tt>) when asked to do so with the <tt>-r</tt> flag
<tt>4.8.0</tt>) when asked to do so with the <tt>-r</tt> flag
(e.g., <tt>ncks -r</tt>).
The development version simply places today's date in place of the
version.
...
...
@@ -1259,9 +1272,9 @@ As of 20131101 there is no Cygwin package for ANTLR, and the netCDF package does
<li>Once you have installed the pre-requisites as shown above, you may then build the latest stable NCO and install it in, e.g., <tt>/usr/local</tt> with: