It could be nice to extend VIPM login feature in a way that it would allow to store list of installed packages based on machines, and LabVIEW versions. When user is logged in - he could create such configurations, and synchronize them across machines. Configuration could be stored online, along with credentials used for VIPM login.
It could allow then to login into VIPM, see and install missing packages on the particular machine.
I know that it is possible to create vipc files, but anyway this does not guarantee that package configuration file will be up-to-date. And, it requires manual work - create vipc, copy somewhere, then transfer to new machine.
Such feature could be useful while installing packages on new machine (customer's machine for the project needs, virtual machine for testing purposes or when developer simply changes his development PC).
Question
kosist
Let me share the following idea.
It could be nice to extend VIPM login feature in a way that it would allow to store list of installed packages based on machines, and LabVIEW versions. When user is logged in - he could create such configurations, and synchronize them across machines. Configuration could be stored online, along with credentials used for VIPM login.
It could allow then to login into VIPM, see and install missing packages on the particular machine.
I know that it is possible to create vipc files, but anyway this does not guarantee that package configuration file will be up-to-date. And, it requires manual work - create vipc, copy somewhere, then transfer to new machine.
Such feature could be useful while installing packages on new machine (customer's machine for the project needs, virtual machine for testing purposes or when developer simply changes his development PC).
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.