I have to question if this is even appropriate for the Getting Started.
The average windows use will be using a precompiled binary. I would
refer to it as per my suggestions in our private exchange with Curt.
Anybody building from source will have already acquired the readme,
which as I stated always has greater potential to be up to date.
Really, we need to inventory and categorize *all* the readme doco,
evaluate it, then break it down, merge all the duplicated stuff
and procede from there.
I need to do this with my own stuff as well since I have duplicated
info on XML and the property manager in the joystick and panel readmes
This of course is just my opinion, but it will save headaches in the
On Fri, 29 Jun 2001, Michael Basler wrote:
> > Curtis L. Olson writes:
> > > The docs-mini/README.Win32 file is in need of an update. It is very
> > > cygwin specific and very out of date. Could we rename this
> > > README.Cygwin and have one of the cygwin developers update the
> > > information in this file so it is current.
> > >
> > > Thanks in advance,
> > I just noticed we already have README.cygwin which is quite different
> > from README.Win32. Perhaps we should just delete the README.Win32
> > after incorporating any still relevant hints/tips from there into
> > README.cygwin. Norman, your name is on the README.cygwin. Can I
> > volunteer you to make sure it is current?
> Do we really need this? I didn't check recently, but for a long time all the
> info therein was doubled in the Getting Started (which was originally based
> on this file, but changed drastically over time).
> I only see sense for it in case someone updates it very closely (i.e.
> T(update)_readme<<T(update)_GettingStarted) according to potential changes
> of Cygwin.
> This is different for README.MSVC which is not and will not be covered in
> the Getting Staretd and thus is required.
> Sincerely, Michael
> Michael Basler, Jena, Germany
> Flightgear-devel mailing list