Jon Berndt wrote:
Hi !
As a user on the FG user list requested a patch from base package
pre2-pre3 in order to reduce download size/time, I was looking for the
required pre2 package, it doesn't seem to be available on
ftp.flightgear.org anymore - so I decided to look what base package I am
currently using in order to see whether I could simply tar my current
base directory and use this as a patch basis, but there doesn't seem to
be any version information included in the base directory either, nor
does fgfs --version provide _any_ information at all, I think
particularly the version information via command line
should be added ASAP, possibly even directly available from within
FlightGear.
I think that's an excellent idea. I also think that fgfs --version should report the
SimGear, JSBSim, YASim, etc. version numbers.
yes, including not only the version of the FlightGear runtime but also
of the FlightGear base package itself, which -as all of us know- might
very well differ from the actual release version.
For the latter to be easily implemented there should be some simple
version file stored into FlightGear's base package root directory,
this would not even need to be XML based, even though that would
certainly not harm at all, if you take things like patches into
account.
Optionally, it might even make sense to provide some more detailed
version information for debugging purposes, e.g. for stuff like
the available plib/openAL libraries etc.
That way, it would also become relatively easy to enable new users
to track down potential problems caused by version conflicts because
of old system libraries etc.
Using fgfs --version one could provide general information about
all relevant version information, more detailed and library-specific
information could be provided by using something like
fgfs --version=plib or fgfs --version=openal.
Boris
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
