On Tue, 14 Jan 2003 21:39:17 +1100, Geoff Reidy <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>:
> Arnt Karlsen wrote: > > > > > ..most people will the source tarballs goes into the /usr/local/ > > tree as told by the docs. When co'ing from cvs, they haul in > > _everything__again_, instead of just update what's new in cvs since > > the tarball release. > > > > As I did, it's been a bit of a learning curve but well worthwhile. > > > > > > Decisions of where to drop the cvs sources has to be made at check > > > out > > > > > > ..yep, but we should advice on the ideal cvs for FG. ..here is where I meant to say "ideal cvs setup for FG". > > Where to install the binaries seems to be another issue :) > > > > >>time and I'm not too sure how to take the pain out of that > >operation. > > > > > > ..you hardcoded '~/games/' painlessly ;-), it should be $FG-CVS-ROOT > > or some such, and just where do we put FG-CVS-ROOT? '/usr/local/'? > > > > Everything's hardcoded here, I think I've done it all the hard way. > > Anyway, I seem to have been trumped by Jon's Perl script. I'll give > that a go and see how it works. > > > > >>Hope noones offended by me having flightgear under games :) > > > > ..<hiring expensive hitman/> ;-) > > Whoops, now I've done it... ..in the market for expensive bodyguards? ;-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
