* someone off list, but IMHO this should be discussed openly: > [...] but the intent is for FG_ROOT to point to a top level > directory (i.e. the root) and beneath that would be bin/ > data/ src/ lib/ include/ etc ....
There's only one reason why we need to point fgfs and associated scripts and tools to some place *at all* (using FG_ROOT or --fg-root): So that they can find the data at runtime. There's no reason *whatsoever* to have a pointer to source files and #includes. And the runtime data directory is that which contains file "version". It's *not* a directory which contains a data/ directory which contains the data. Making the layout optional was a bad idea 10 years ago, and it is a bad idea today. Even worse, as we have many more users and it bites us a lot more often in the ass than it used to. My intention is to remove the disgusting hack that checks for an existing data/ dir and that appends it if found, and that before the 2.0 release. > Pointing FG_ROOT at /full/path/data is allowed because of historical > precident. I'm not an archeologist, and I don't think we should look at what seemed to make sense a decade ago. What we have now doesn't make sense. It leads to bugs and confusion, while not having a *single* advantage. Or could anyone tell me one, please? Just one? > It might make sense to have FG_DATA which defaults to $FG_ROOT/data/ What for? FG_ROOT shall point to the directory which contains the data (i.e. the file "version"). We don't need another variable. If anyone wants one that points to the source, then s/he can define that one on his/her computer. Of course, we can rename FG_ROOT to FG_DATA, but that's a lot of work for little gain. m. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
