Damon Kwok

> Allowing for corral in some fashion to download and build libraries from source and then install them in a pony specific fashion however, seems doable and something we want...

Awesome

> Do you have ideas on how this would be implemented? Yes.It looks like Leiningen's template system: https://github.com/technomancy/leiningen/blob/master/doc/TEMPLATES.md

Not a simple copy. When a project is created using a template, it will automatically download the dependencies specified in corral.json.

corral.json is part of the template, the author of the template has built in the required dependency information

For example: ``` corral new hello ``` You will get this directory: ``` hello ├── corral.json ├── CHANGELOG.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── examples │ └── simple-example │ └── simple-example.pony...

To put it simply: initialize a pony project with a specific structure and automatically download dependencies.

Yes, it will be a is a direct copy of how `Leiningen` works. I think the meaning of the template system is to help people quickly clone an existing engineering...

About templates, I think the problems of corral and `lein` are similar. We can learn from its ideas.

It's hard to say which way is better, even the design of the `Cargo` and `npm` are rated as bad. This is the radical approach of deno's designers: ```ts import...