> Anyway, like I said, I'll go with the flow on whatever the consensus is, > but I would really prefer a situation where rm -rf Aircraft/whatever > would remove an entire plane. Does it make sense? To me, yes.
I would like every directory to contain a file that lists the relative path to every external directory (i.e. starts "../") that contains one or more files that is assumed to be present by this directory. If there are no external dependencies, I think the empty file should exist. That allows incremental install of aircraft and of scenery segments that use shared drop-in objects. A single script can walk the whole installed base and identify missing pieces automatically; in conjunction with the CVS server it can also trivially retrieve the missing stuff (on Linux). Imagine the script is called "please-install" and adds any cmdline params to the list of directories that would be identified by the tree scan ... $ ./please-install Aircraft/shuttle Checking out the base for the first time, you specify the "-l" flag to get just the top level directory, which contains a dependency file with the absolute minimum files to even have FGFS start running. Just running the please-install script with no parameters will pick that stuff up. A trivial little test inside the script can recognise references to the scenery directories and instead download (and unpack) the tarballs. > Is there any reason to uninstall a plane? Not for me, but some user > (read "not developer")might have a reason. When I download something which turns out to be too large for my video card ... and I want the megabytes of disk space back. In conjunction with the please-uninstall script, this viable and reasonably safe to do. I'd expect the script to do a "cvs release" (for tidyness) followed by a tree walk to find directories that _were_ dependencies and are not listed by any other directory's dependency and so can now also be dumped. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
