On Sat, 19 Mar 2011 17:42:23 +0000, Chris wrote in message <1300556543.16575.17.ca...@chris-desktop.home>:
> Hi Tomek, > > That dependency model was chosen as its not required to download the > base aircraft or the base model set to use FlightGear. > > To run FlightGear you need a plane, the base aircraft package only > includes a fraction of the aircraft available for FlightGear, the > others are available to download at the FlightGear website and these > will allow you to run FlightGear. You also don’t need the scenery or > models to run FlightGear however as you have found out you run in to > problems if you omit either. > > If you made these packages dependencies, it would stop users such as > myself for installing the FlightGear binary package, but using my own > scenery and aircraft. If using terrasync, the models package needs > removing and replacing with the models released by upstream as some of > the latest models cant be found in the package released by Debian. > > At the moment Debian does not handle the amount of data produced by > the FlightGear project well, this is because the tools are just not > there yet. > > I still feel this is the best dependency solution. > > Chris ..I agree for Sid and Experimental, for stable and testing, I respectfully disagree and submit a wee patch. ;o) ..another way is use my try at a control file as a starting point to create a "flightgear-with-everything" meta package, at least Installed-Size is wrong. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case.
control-flightgear-with-all-2.0.0-4RC0
Description: Binary data
patch-2.0.0-4RC0
Description: Binary data
