[Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Tom Russo]

On Tue, Sep 14, 2010 at 10:29:03AM -0700, we recorded a bogon-computron collision of the <curt.we7u at gmail.com> flavor, containing:
> On Fri, 10 Sep 2010, Dean Groe wrote:
> 
> > I am puzzled as to why I would bother to make after configure already told me 
> > that it was old, that my src was not updating?
> 
> Yea.  Once configure tells you the version number and it's wrong
> there's no need to go further.
> 
> 
> > FWIW, it appears that the problem was due to CVS not updating source.  I 
> > downloaded source and built in a different directory and it worked OK.
> 
> > Of course, that is not how this is supposed to work ideally, but that is what 
> > was needed this time.
> 
> Probably becase you tried the STABLE or RELEASE tags and those
> options are sticky, as Jerry mentioned.  Jerry wrote:
> 
> > > Use 'cvs update -r HEAD'  instead of STABLE or RELEASE. The use of
> > > any tags in an update is sticky. You get what you asked for in
> > > this case.
> 
> So if you had issued that command against your original directory
> you probably would have been able to then issue the "cvs update"
> command and gotten the latest CVS HEAD sources.  Perhaps you still
> have that directory around and can try it.

What you want to do is use the "-A" option to CVS update.  According
to the documentation:

              Use the -A option  to  reset  any  sticky  tags,  dates,  or  -k
              options.  (If you get a working file using one of the -r, -D, or
              -k options, cvs remembers the corresponding tag, date, or  kflag
              and  continues  using it on future updates; use the -A option to
              make cvs forget these specifications, and retrieve the  ``head''
              version of the file).  Does not reset sticky -k options on modi-
              fied files.

So simply doing "cvs update -A" in the checkout directory will undo the
stickiness and retrieve the HEAD version -- no need to use "-r HEAD".  From 
that point forward, all updates in that directory will continue to update to 
the latest.

As Jerry and Curt say, using -r at all makes the tag sticky, and all 
subsequent cvs updates merely update to the latest with that tag.  Since we 
only move RELEASE tags after the very rare releases, that means they'll usually 
do nothing.  We don't move STABLE tags all that often.

After clearing sticky tags with -A, watch for update lines that start with C 
--- these indicate a problem with the checkout (conflict) that usually result 
in a mangled file that will produce compilation errors.  Simply remove the 
mangled file that is listed with C and redo the update.  The latest, clean 
version of the file will be retrieved after a message that it was lost.
This is especially a problem if you've done any personal editing of source
files between updates.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 "The truth will set you free, but first it will piss you off."