Re: Why does the default cpath not have lib?.so in it?

[Luiz Henrique de Figueiredo <lhf@...>]

> The default package.cpath on linux has ./?.so and a few others, but it
> seems like it also ought to have a ./lib?.so variant.

You're free to add this to your package.cpath if you need it.
But one reason not to use libxxx.so is to avoid clashing with
system libraries. For instance, an MD5 library for Lua might
conflict with a libmd5.so from the system. (It actually did
once in an old Linux.) Actually, you're free to call your
libraries anything you want; just adjust package.cpath.
I don't think you even need a .so extension.