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

Should dependencies be downloaded and installed for each package by default? #6

Open
kobbled opened this issue Sep 7, 2021 · 0 comments
Labels
question Further information is requested

Comments

@kobbled
Copy link
Owner

kobbled commented Sep 7, 2021

Currently by default rossum only builds the main package not its dependencies. you can select to build all the dependencies as well but you have to have them downloaded on your system with an environment variable pointing to the parent library directory. Should this be opposite, in that it defaults to build all the packages and dependencies in a "target" or "build" folder? Where the user can specify if they don't want to build dependencies instead (for quicker debugging purposes). Rust and nodejs do the later, downloading and building all dependencies in the target folder. Setting up a download registry might be a bit out of scope for me, but the dependency web is become an issue, and could be handled better. Can just use git clone calls as well, where rossum just holds a file with library download locations. Would be like

rossum add math

would download math to a temp folder, or into the "target" folder, and automatically link it in the package.json file. ninja, or rossum build would compile the dependency to the "build" or "target" folder. This might take a long time to first build a package, and require a wrapper script or manager script to manage the downloaded dependencies, and to show a progress bar in the console instead of a wall of text from git clone calls.

@kobbled kobbled added the question Further information is requested label Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant