["hadriel.kaplan@xxxxxxxxxx" <hadriel.kaplan@xxxxxxxxxx>]

The problem is if you write a plugin for others to use, requiring them to compile code is a high bar to expect.  So if it's more than just another pure lua lib which doesn't need c-code to be compiled, as a file/dir accessor would need, it's tough. :(

Sent from my iPhone

On Feb 8, 2014, at 6:38 PM, Tony Trinh <tony19@xxxxxxxxx> wrote:

Guy Harris wrote:
...
Should we either bundle the LuaFileSystem stuff, at least on platforms where we bundle Lua with Wireshark rather than relying on the OS to have it as a package (I guess the packager could make the appropriate Wireshark package depend on the LuaFileSystem package, if one exists), or do our own Lua extensions using the wsutil routines?
...

IMHO, that's beyond the scope of the Wireshark Lua API, which should only provide APIs specific to Wireshark functionality that cannot be [easily] accomplished with third party libraries (which are plentiful). In this case, portable filesystem calls can be achieved with Penlight [1]. Regarding the specific directory-creation example you cited, use pl.dir [2].

[1] http://stevedonovan.github.io/Penlight/api/index.html

[2] http://stevedonovan.github.io/Penlight/api/modules/pl.dir.html#makepath

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe