[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#361740: liblua50-dev: symlink pointing to .

Justin Pryzby <justinpryzby@users.sourceforge.net> writes:
> On Sun, Apr 09, 2006 at 04:30:06PM -0700, Russ Allbery wrote:
>> Justin Pryzby <justinpryzby@users.sourceforge.net> writes:

>>> Package: liblua50-dev
>>> Version: 5.0.2-6
>>> Severity: normal

>>> $ dpkg -c /var/cache/apt/archives/liblua50-dev_5.0.2-6_i386.deb  |grep -- '->'
>>> lrwxrwxrwx root/root         0 2006-04-09 10:03:01 ./usr/lib/liblua50.so -> liblua50.so.5.0
>>> lrwxrwxrwx root/root         0 2006-04-09 10:03:01 ./usr/include/lua50/lua -> .

>> Why is this a bug?  I'm missing something, I think.

> Is it deliberate?!  Why would one need such a symlink?  It bothered me
> because my grep -r /usr/include/ gave me a recusion warning..

Does grep -r follow symlinks?  That sounds kind of dangerous.

I haven't ever used or uploaded the package, so I'm not sure, but my guess
is that it's so that software built with -I/usr/include/lua50 that
includes files like #include <lua/foo.h> will find the header files.

There are other ways to accomplish the same thing, but I would have been
tempted to do that myself, if that is indeed the problem being solved.

Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Reply to: