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

Transition to package infrastructure #2

Open
quantum9Innovation opened this issue Oct 13, 2024 · 1 comment
Open

Transition to package infrastructure #2

quantum9Innovation opened this issue Oct 13, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@quantum9Innovation
Copy link
Member

quantum9Innovation commented Oct 13, 2024

Install, build, and running phases should be fully reproducible (this issue may require a whitepaper—#3)

Devenv seems like a promising solution; optional-use containers can be used to create provably reproducible environments

@quantum9Innovation quantum9Innovation self-assigned this Jan 19, 2025
@quantum9Innovation quantum9Innovation added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Jan 19, 2025
@quantum9Innovation
Copy link
Member Author

While it is common practice to run arbitrary shell scripts inside development shells, this is far from an ideal setup. Development shells are typically intended for rapid experimentation where this type of behavior may be more suitable, but for robust testing (e.g. in CI and even for local development) it will be necessary to ensure verifiable reproducibility. Shell scripts can potentially rely on packages that already exist on a specific system and utilize those configurations, making it impossible to determine whether the dependencies for a shell script have been appropriately included in the development shell and whether those specific versions are the ones being used. This can be easily solved by packaging each of the scripts and running the package (which will not even require using a development shell) to install the all_seaing_vehicle repository, build subpackages, and run nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant