2,561
edits
m (adding related discussion) |
(linking to forum topic) |
||
| Line 5: | Line 5: | ||
This is mainly because of the fact that different people may have different requirements when it comes to aircraft status and are thus viewing the status from different angles, possibly neglecting progress in other areas. | This is mainly because of the fact that different people may have different requirements when it comes to aircraft status and are thus viewing the status from different angles, possibly neglecting progress in other areas. | ||
In addition, users are frequently facing issues when it comes to determining compatibility requirements between aircraft tarballs and fgfs binary releases (see for example [http://flightgear.org/forums/viewtopic.php?f=6&t=2814]). This very issue is further complicated by the fact, that FlightGear in general doesn't expose any detailed version information that could be queried by arbitrary FlightGear resources (such as aircraft). Furthermore, it is questionable whether simply starting to expose version information in the property tree would be sufficient, i.e. for scenarios where individual features may be removed/added or modified in CVS/HEAD, which however wouldn't necessarily result in a modified version number, so that such modifications wouldn't be easily communicated to FlightGear resources that depend on such features and information (for a more in depth discussion of this particular issue, please see [http://wiki.flightgear.org/index.php/Simplifying_Aircraft_Deployment#Version_tracking.2FCompatibility_checking]). | |||
=== Scope === | === Scope === | ||
edits