On Mon, Dec 24, 2001 at 01:42:45AM -0500, Ben Collins wrote: > On Mon, Dec 24, 2001 at 04:01:25AM +0000, Adam Olsen wrote: > > > > On Sun, Dec 23, 2001 at 10:49:33PM -0500, Ben Collins wrote: > > > On Sun, Dec 23, 2001 at 06:57:45PM -0800, Thomas Bushnell, BSG wrote: > > > > > > > > Ben Collins <[EMAIL PROTECTED]> writes: > > > > > > > > > But quake2-engine does not depend on anything to fulfill it's purpose. > > > > > It is a gaming engine, not a game. This is the same logic that applies > > > > > to libraries and interpreters. > > > > > > > > Huh? The purpose of quake2 is not to run quake levels and be a > > > > playable game? > > > > > > The purpose of the sources released is a gaming engine. They did not > > > release "quale2 the game", which is what the data files consist of. > > > Notice that lots of games from Id are based on the quake3 engine. They > > > aren't quake3, but they use the same engine, and different data files. > > > > > > Do not confuse a game engine (the source released) with the game itself > > > (the data files that they didn't release). > > > > But you do agree that it requires having *some* data, no matter what > > "game" it's for? Which means having a Depends: quake2-data? > > > > And if you wish to argue that it can be used to develop the data, then > > you should have no problem in providing such a package of it. > > Does python "Depend: some-python-script"? No, it doesn't. Python is an > interpreter. Same logic applies for the quake2 engine. Other things will > depend on it, not the other way around.
No, it doesn't apply, because quake2 is an engine for a game, not an interpreter for a language. -- Adam Olsen, aka Rhamphoryncus