Updating a Baselibs Component: Difference between revisions

== Process of Updating A New Component to Baselibs ==

This example document will detail the process that was used updating netCDF 4.3.2 into GMAO Baselibs.

In this case, we were updating netCDF-C 4.3.2 to GMAO-Baselibs-4_0_5. So, the "internal" tag we went to was 4_0_6. In a temporary directory (say, NewBaselibs) you checkout Baselibs and tag relative so you know where you started from. You also make sure the tag you're making doesn't exist:

   $ cd /discover/swdev/mathomp4/Baselibs/NewBaselibs

   $ bcvs co -kk Baselibs

   $ bcvs tag -r GMAO-Baselibs-4_0_5 Internal-4_0_6-before-netCDF-4_3_2-NCO-4_4_4-cURL-7_37_0

   $ bcvs tag -d Internal-4_0_6

=== Unpack the new library ===

First, move to a directory that can contain your "new import",

   $ cd /discover/swdev/mathomp4/Baselibs/NewImports

   $ tar xzf netcdf-c-4.3.2.tar.gz

and move into the new directory directory:

   $ cd netcdf-c-4.3.2

=== Import the new package ===

First, do a dry-run import of the package (note the <tt>-nq</tt>):

  $ bcvs -nq import -kk -m "MAT: Import netCDF-C 4.3.2 retrieved 2014-JUN-10 from https://github.com/Unidata/netcdf-c/releases/tag/v4.3.2" Baselibs/src/netcdf Unidata release-4_3_2

If everything looks okay, then actually import the package:

  205 conflicts created by this import.

  Use the following command to help the merge:

 

 

Go back to your new Baselibs tree:

Then, checkout/update to new release:

and remove -n and run again once satisfied.

C ncdump/dumplib.h

C nctest/driver.c</nowiki>

Note in this case that many conflicts were found. If there were conflicts, you should resolve them. When in doubt, I suggest always using '''only''' what the new package contained. The only exceptions might be in Makefiles or other files that might have been edited by Denis or other maintainers to get it to build with the other Baselibs. But, if at all possible, go with the stock library.

  $ bcvs commit -m "MAT: merge new netCDF-C 4.3.2 import, many conflicts resolved"

Repeat the above steps for any other packages you want to update as well.

To make your new tag, first do a relative tag at the <tt>src/</tt> level:

   $ cd ..

   $ bcvs tag -r GMAO-Baselibs-4_0_5 Internal-4_0_6

Then, for safety's sake, '''untag''' the new library and retag the against the new vendor release tag:

  $ bcvs tag -d Internal-4_0_6

Next, edit the usual metafiles (<tt>Changelog</tt>, <tt>CONTENTS</tt>, and <tt>VERSION</tt>) as well as any needed make system changes and commit those on the HEAD. Then, push your new tag on those files:

  $ bcvs tag -F Internal-4_0_6 ChangeLog CONTENTS VERSION

=== Verify new tag ===

The final step is to checkout the new tag and build the Baselibs per usual. My first step is to usually do a <tt>cvscmp</tt> against the old tag to make sure everything looks sane. I then like to do a <tt>diff -r</tt> between the updated library and the stock package that was downloaded from the web. Hopefully, all is well.

If everything works, you can then delete your "before" tag and if all '''really''' works, rename the <tt>Internal</tt> tag with an official <tt>GMAO-Baselibs</tt> tag.