You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2016/08/17 22:37:20 UTC

[jira] [Commented] (TS-4762) Improve the Lua package import paths.

    [ https://issues.apache.org/jira/browse/TS-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425524#comment-15425524 ] 

James Peach commented on TS-4762:
---------------------------------

[~zwoop] [~kichan] [~jesus] any ideas?

> Improve the Lua package import paths.
> -------------------------------------
>
>                 Key: TS-4762
>                 URL: https://issues.apache.org/jira/browse/TS-4762
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Lua
>            Reporter: James Peach
>
> I noticed that when you build ATS with a non-default prefix, you end up with unexpected Lua package paths.
> For example, this is what I had for {{package.path}}:
> {noformat}
> ./?.lua;/n/trafficserver/share/luajit-2.0.4/?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/n/trafficserver/share/lua/5.1/?.lua;/n/trafficserver/share/lua/5.1/?/init.lua
> {noformat}
> Maybe we can think of a way to automatically get the right paths for the platform.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)