On Sun, 6 Nov 2011, Gary Neely wrote: > This topic raises a point about distribution of non-critical files. > For example, my 1049H Constellation has a number of large files that > aren't necessary for flying the plane. I have source PSDs for > livery-makers, and Yakko's terrific How-to for flying the 1049H. Both > are directly beneficial to interested Flightgear users, but not > essential, and both sets are large files (10MB or so each) that would > bloat the plane's base distribution. Currently these are maintained > and available at my home site. > > Provided that all materials are GPL, it would be nice to attach them > somehow to the plane as a kind of optional secondary download, a sort > of 'developers kit'. Does this concept make any sense? Would it be too > seldom-used to be worth it? Is it even possible? Or are others already > way ahead of me on this kind of idea?
Now that we have per-aircraft repositories I plan to add my "source" material (blender, svg, datcom, octave, gerris etc files) below a dev directory in the aircraft's repository. Probably further structured in FDM, models, ... subdirectories. If we use a small set of names (I'd suggest dev, development or src) for the base directory of such files it shouldn't be too hard to make the aircraft packaging script(s) omit these files from the release .zip files. Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://gitorious.org/anders-hangar http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
