NOTE WELL: If
is upgraded on
and another release of
is planned, that tarball will be using the new
! (Also note that this means that upgrading
means there will be a relatively short validation cycle, as we would tend to want to do this just before a new release of
, at the end of a
I may have a solution to this - on whimsy I'll just run
and if I need to use the older
tarball we should be OK.
Fetch, build, and install the target version of
- See if any of the following need to be updated:
- Reconcile any
autogen file overrides we ave placed in
tar xvzf `autoopts-config libsrc`
diff -ur libopts* | grep '^Only' and look for things other than
bk rm -f any files that are no longer needed
diff -ur libopts-* libopts | grep '^diff' and use that output to copy the updated files from
- Add the following to any updated
+AM_CFLAGS = $(NTP_HARD_CFLAGS)
+AM_CPPFLAGS = $(NTP_HARD_CPPFLAGS)
+AM_LDFLAGS = $(NTP_HARD_LDFLAGS)
bk ci -y'Updated to libopts-whatever' (is this the right place?)
:run-autogen (this script is in
ntp-dev as that's the only place we would ordinarily be updating
- Make a note in the
ChangeLog and check that in.
check it out, build it, and:
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
scripts does a
option this should not be a problem at all.)
is being updated the snapshot roll will need a
before it runs.
may not do this for us...