[luatex] Finding user-specific Lua binary packages

[luigi scarso]

On Mon, Mar 16, 2015 at 10:31 AM, Dirk Laurie <dirk.laurie at gmail.com> wrote:

> 2015-03-16 10:04 GMT+02:00 luigi scarso <luigi.scarso at gmail.com>:
> > On Mon, Mar 16, 2015 at 8:33 AM, Dirk Laurie <dirk.laurie at gmail.com>
> wrote:
> >> The manual says they are looked for in
> >>
> >>     CLUAINPUTS=.:$SELFAUTOLOC/lib/{$progname,$engine,}/lua//
> >>
> >> but this path seems not to provide for $HOME/texmf. I could put
> >> a symbolic link to the .so files in `.` every time, but that really
> >> defeats the purpose of kpse.
> >
> > here
> > $ kpsewhere core.so
> >
> /opt/luatex/standalone-mkiv-new/tex/texmf-linux-64/bin/lib/luatex/lua/swiglib/qpdf/5.0.1/core.so
>
> This tells me that on your system,
>
> SELFAUTOLOC=/opt/luatex/standalone-mkiv-new/tex/texmf-linux-64/bin
>
> Presumably SELFAUTOLOC is where the TeX binaries are. On Ubuntu,
> they are in /usr/bin. It is hardly proper for an ordinary user, even one
> with
> sudo permission, to make a directory /usr/bin/lib/luatex/lua/ for personal
> stuff, but I have checked that doing so, besides giving one a thrill like
> sneaking into the headmaster's office when he is not there, does work.
> And that /usr/local/bin/lib/luatex/lua/ and $HOME/bin/lib/luatex/lua/ do
> not.
>
> So, at present the bottom line seems to be: user-written Lua scripts
> are OK for LuaTeX, but user-written C modules are OK only for those
> with superuser status.
>
well a C modules compiled is a binary, so it could be reasonable.
But in any case
package.loadlib (libname, funcname)
should work (libname is something like /<my_path>/core.so).

-- 
luigi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/luatex/attachments/20150316/f8c3f9ce/attachment-0001.html>