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

build tagging #3

Open
rdecarreau opened this issue Jul 1, 2020 · 1 comment
Open

build tagging #3

rdecarreau opened this issue Jul 1, 2020 · 1 comment

Comments

@rdecarreau
Copy link
Owner

We had to start talking about dependencies at some point. Here we are.
How do we manage the various versions of installed tools?

Tags on the image are a great place to start, then maybe host those images in a registry?

@rdecarreau
Copy link
Owner Author

"Various versions of installed tools" presents a unique challenge with LabVIEW. A lot of the drivers try to do things with the low-level OS, hardware, etc and won't install.
Clearly a problem with containerizing from the get-go, access to hardware buses will be non-existent/limited. The question is, how much of that do we need? What test applications are we trying to run? Does compilation require the entire driver? Can we get away with just the vi.lib vi's? Probably not but just brainstorming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant