[mythtv-users] A Question about CVS Upgrading

[Robert Tsai]

On Wed, Apr 06, 2005 at 10:09:16PM -0600, SpikeyGG wrote:
>   I've been using CVS for a little while longer than I've been using
>   Myth, but I still don't know the answer to this...  I fairly
>   regularly run a "cvs update" in the mythtv directory to keep it up
>   to date.  Which one of the following actions (or one not listed)
>   should I be doing for an update?
> 
> 1. "cvs update", then "./configure", then "make", then "sudo make
> install" (hopefully overwriting the old stuff)
> 
> (or)
> 
> 2. "make uninstall", then "cvs up", then "./configure", then "make",
> then "sudo make install" (to "cleanly" upgrade)
> 
> Mainly, I'd like to know if doing #1 will screw stuff up, or will it
> just overwrite the libraries and binaries that I've already got? I'd
> like to know this not only for Myth but other programs and code that
> I use with CVS.

I've been doing (1) for awhile with no problem (except that
currently-running myth programs can crash when their files have been
rudely overwriten). So (2) is probably "nicer". It will also get rid
of old-version detritus (e.g., libmyth-xxx-0.17.so) when version
numbers get bumped.

As for Myth plugins, I've sometimes had weird dependency problems (I
think; logfiles complain about library versions) where not enough
stuff was being recompiled; a "make clean" in the various plugins
directories generally fixed those problems.

--Rob