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

Add on-demand vendoring for packages / proper dependency management #3504

Open
fschutt opened this issue Jan 19, 2023 · 1 comment
Open

Add on-demand vendoring for packages / proper dependency management #3504

fschutt opened this issue Jan 19, 2023 · 1 comment
Labels
🎉 enhancement New feature! 🕵️ needs investigation The issue/PR needs further investigation priority-low Low priority issue

Comments

@fschutt
Copy link
Contributor

fschutt commented Jan 19, 2023

Right now the dependency management in the wasmer.toml is in an infancy state, we need to figure out how / when to vendor packages to make them self-contained on-demand.

We should also test that things like std::process::Command::new("python") works from inside a natively-compiled executable, if said executable is vendored. This means that process / environment management has to be aware of all the commands that are currently available inside of the container (could be difficult).

@fschutt fschutt added the 🎉 enhancement New feature! label Jan 19, 2023
@syrusakbary
Copy link
Member

syrusakbary commented Jan 24, 2023

This issue can be split into two sides:

  • How packaging can describe and use dependencies. We need an architecture document that @Michael-F-Bryan will handle
  • How dependencies will be downloaded when using a package. It seems this is partially achieved in WASIX in the wasix branch

@syrusakbary syrusakbary added the 🕵️ needs investigation The issue/PR needs further investigation label Jan 24, 2023
@ptitSeb ptitSeb added the priority-low Low priority issue label May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎉 enhancement New feature! 🕵️ needs investigation The issue/PR needs further investigation priority-low Low priority issue
Projects
None yet
Development

No branches or pull requests

4 participants