On Sun, 2006-04-09 at 18:23 -0700, Russ Allbery wrote: > > There is exactly one header file, and IMO packages should care enough > > about their dependencies to not do silly things to get a single file > > included. > It smells like a transitional measure, but I don't know for sure. I see > that it was intentional:
It was indeed intentional > I do generally agree that it's not the best idea if there are other > solutions to the same problem, but I can see why one might arrive at this > solution. And the exact reasoning is thus... Some programs are written aware of the lua50 and lua40 dirs used in Debian and other distros. They do: #include <lua50/lua.h> Some are aware and do: #include <lua.h> and have -I/usr/include/lua50 Some are aware and do: #include <lua/lua.h> and have -I/usr/include/lua50 Some are unaware and do either of the second without the -I -- at that point it's up to the packager to fix up the build either by adding a -I or by fixing the #include statements to be more correct. There is a wealth of software out there which uses Lua, and not all of it is suited to a packaged version of Lua and those which are are not always suited to the idea that there might be differing versions on the filesystem at the same time. This is a compatibility measure in an attempt to increase the amount of software which can build with as little intervention as possible from the packager. Also, it's not just one include file. It's just that others are in liblualib50-dev I imagine. Regards, Daniel -- Daniel Silverstone http://www.debian.org/ PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895
signature.asc
Description: This is a digitally signed message part
