Dear Benjamin,
Thanks for your comments. Actually, we need clear statements to updated the
Guide.
> 1. We should immediately attempt to fix all known errors or
> inaccuracies in
> the FlightGear installation documentation. More people are wasting more
Okay. I would *love* do this. Just take over my work load for a living for
the next three days, and I'll start immediately.
Seriously, if you feel you've got some spare time you might think about
contributing to the documentation. Just contact me under [EMAIL PROTECTED] (Or,
you might contribute in other fields as well.)
At present, I don't find time to do updates more than twice a year. Next
round is planned for spring.
> 2. I did not download a CVS snapshot for my installation (nor do
> I think I
> should have done so). I downloaded the gzipped tarballs from
> FTP. Unless I
> do not understand properly how these FTP source files are created
> or managed
> (vis a vis CVS), I am of the (very firm) opinion that these FTP
> source files
> should definitely compile without issues. i.e., A new user using a
> reasonably up-to-date gcc compiler (e.g. 3.2) who properly downloads and
> installs these source files should have a clean compile.
As far as I know, these tarball are created form the CVS archive on the fly,
which means they are not necessarily error-free.
If you want a - mostly - error free version, I'd suggest the latest release
version, which should compile/install cleanly.
> 3. As has been suggested recently by others, the list of
> *necessary* (basic)
> configure/compilation options should be very clearly specified
> for new users.
> Advanced configure/compilation options should be referenced as such
Agreed. We'll change this. Which options are currently default and which one
should be named/not named?
Regards, Michael
--
Michael Basler, Jena, Germany
[EMAIL PROTECTED]
http://www.geocities.com/pmb.geo/
_______________________________________________
Flightgear-users mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
