-
Notifications
You must be signed in to change notification settings - Fork 110
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
Narrow in scope to use more "ecosystem" features and less "package" features #172
Comments
After some more research, objects/arrays cannot be passed as part of the options object yet. There is an open issue to add arrays. devcontainers/spec#57 In the meantime, the suggestion seems to be to use spaces or commas as delimiters. |
@DaneWeber @danielbraun89 I got a test working! 😊🎉 link to repo |
Looks awesome! IMO the official python feature should have the same treatment. |
NVM saw you already addressed it in https://github.com/devcontainers-contrib/features/discussions/171#discussioncomment-4300704 |
Some notes:
|
My opinion on packages being part of features has shifted negatively. It may shift back to positive at some point. Discussion on package installation being a part of features and scope of images vs features vs postCreateCommand in devcontainers-contrib/.github#4 |
@danielbraun89 I'm closing this open-ended issue in favor of more specific and focused issues. I think this discussion is a good one, but it belongs more in discussions at this point, with issues focusing on concrete tasks instead. (Hence, closing this) |
Opened in response to the discussion in #171. This is an issue tracking implementation progress.
After some consideration and discussion in #171, I think the scope of this repo should be severely restricted. Sure, lots of other features can be added like Haskell, Heroku's CLI, etc. should all be included... But I don't think we need a
jest
package if we add a "packages" field of some kind to a generic Node.js feature. This is my opinion.TL;DR: Make generic ecosystems like Haskell, Python, Node.js, etc. accept arbitrary package installers instead of splintering them into their own features.
See advantages/disadvantages in #171
"Official" statements regarding the goal/scope of container features
Tasks
The text was updated successfully, but these errors were encountered: