UpdatingLibopts < Dev

---+ Updating =libopts=

%ICON{warning}% NOTE WELL: If =autogen= is upgraded on =whimsy= and another release of =-stable= is planned, that tarball will be using the new =autogen=!  (Also note that this means that upgrading =libopts= means there will be a relatively short validation cycle, as we would tend to want to do this just before a new release of =-stable=, at the end of a =-dev= cycle.)
I may have a solution to this - on whimsy I'll just run =../configure --prefix=/usr/local/gnu/autogen-X.Y.Z= and if I need to use the older =autogen= for a =-stable= tarball we should be OK.

Fetch, build, and install the target version of =autogen=.

   * See if any of the following need to be updated:
      * =sntp/include/autogen-version.def=
      * [[Main.SoftwareDevelopment#Tools_Needed_to_build_from_a_Bit][Main.SoftwareDevelopment]]
   * Reconcile any =autogen= file overrides we have placed in =sntp/ag-tpl/*= .
   * =cd sntp=
   * =tar xvzf `autoopts-config libsrc`=
   * =diff -ur libopts*  | grep '^Only'= and look for things other than =Makefile.in= or =SCCS=.
   * =bk rm -f= any files that are no longer needed
   * copy over and =bk add ...= any new files
   * =diff -ur libopts-* libopts | grep '^diff'= and use that output to copy the updated files from =libopts-whatever= to =libopts=
   * Add the following to any updated =libopts/Makefile.am=
<verbatim>
...
MOSTLYCLEANFILES        =

+AM_CFLAGS       = $(NTP_HARD_CFLAGS)
+AM_CPPFLAGS     = $(NTP_HARD_CPPFLAGS)
+AM_LDFLAGS      = $(NTP_HARD_LDFLAGS)

libopts.c:              $(BUILT_SOURCES)
...
</verbatim>
   * =bk ci -y'Updated to libopts-whatever'= (is this the right place?)
   * run =:run-autogen= (this script is in =ntp-dev= as that's the only place we would ordinarily be updating =libopts=)
   * Make a note in the =ChangeLog= and check that in.

check it out, then:

   * =./build=
   * =cd A.whatever && make distcheck=

Once any problems have been fixed and any changes have been checked in:

   * =bk commit -y'Updated to !AutoGen-1.2.3 and libopts-4.5.6'=

Watch some of the perms on the generated files.
This should not be a problem because the =:run-autogen= scripts does a =chmod u+w= .
(Now that =autogen= supports the =--writable= option this should not be a problem at all.)

*N.B.:* If =libopts= is being updated the snapshot roll will need a =make clean= before it runs. =ntp_configure_cache_version= in =configure.ac= may not do this for us...
This topic: Dev > WebHome > UpdatingLibopts
Topic revision: r18 - 2020-09-16 - 08:54:48 - HarlanStenn