You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v0.2, YALP supports package lookup (via the require function) using two patterns: scriptfiles/lua/?.lua for Lua packages, and plugins/lua/?.dll or plugins/lua/?.so for C packages. An example of a Lua package: lcmd.
Since these packages work in a similar way to Pawn (and the Lua packages depend on YALP), it would be nice to have a support to specify the dependencies, main files etc. even for non-Pawn packages.
The text was updated successfully, but these errors were encountered:
So my plan for this is initially quite lazy: ensure-time plugins. These would behave similar to build-time plugins, simple shell commands you can specify to run. These would be run before the ensure stage.
I'm still not entirely sure on the implementation details but it shouldn't be too difficult. Then, you can write whatever form of application/script you want that would run whenever dependencies are ensured. (Or maybe a specific dependency?)
Since v0.2, YALP supports package lookup (via the
require
function) using two patterns:scriptfiles/lua/?.lua
for Lua packages, andplugins/lua/?.dll
orplugins/lua/?.so
for C packages. An example of a Lua package: lcmd.Since these packages work in a similar way to Pawn (and the Lua packages depend on YALP), it would be nice to have a support to specify the dependencies, main files etc. even for non-Pawn packages.
The text was updated successfully, but these errors were encountered: