Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for non-Pawn packages #265

Open
IS4Code opened this issue Oct 27, 2018 · 1 comment
Open

Support for non-Pawn packages #265

IS4Code opened this issue Oct 27, 2018 · 1 comment

Comments

@IS4Code
Copy link

IS4Code commented Oct 27, 2018

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.

@Southclaws
Copy link
Owner

Thanks for reminding me about this!

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?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants