Once you get cvs working, try out the 'update-xastir' script which will automate the whole process.
Bob, N7XY On Jan 14, 2011, at 4:30 PM, Murry B wrote: > Thanks. > Those are all installed, plus in the configure the > only thing left out was "gpsmanshp" and I > don't think I really need that. > > VE9MB > > > > On 01/14/2011 04:14 PM, Curt, WE7U wrote: >> On Fri, 14 Jan 2011, Murry B wrote: >> >>> As in a previous message, I have Xastir working now, installed from source. >>> What is the safest way to change to cvs update >> >> If you've already installed from sources, then you've got all or nearly all >> the tools you need ready and working, plus the libraries Xastir is looking >> for already installed. About all you need extra are: >> >> autoconf, automake, cvs >> >> Safest is to just create a new directory for the CVS version. That way you >> don't mess up the other (just in case, until you feel comfortable with CVS >> and feel like deleting the other directory and sources). >> >> Follow the README.CVS file's instructions (or the WIKI page) regarding the >> two CVS commands you need to invoke. >> They will create a new subdirectory "xastir" underneath where you are >> sitting in your shell. Then: >> >> cd xastir >> ./bootstrap.sh >> ./configure >> make >> sudo make install >> >> And you're done! >> >> Any time you want to snag the latest: >> >> cvs update >> >> If any files get updated, follow the bootstrap, etc steps above to compile >> and install the new version. >> > > _______________________________________________ > Xastir mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
