Missing system dependency when installing package

[Anton Sundqvist]

Hi all, 

I am maintaining a package and got a user reporting the issue described here: https://github.com/Astemes/astemes-lunit/issues/1

The package installs some LabVIEW native CLI operations and as they go into the directory "C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI" and turns up as a system package. For some reason, at least one user is experiencing issues with this system dependency.

I cannot reproduce the issue on my end and would appreciate some help to solve this. Any ideas on what could be the cause for this?

Thanks, Anton

[Jim Kring]

Hi @Anton Sundqvist

My guess is that the permissions are such that only administrators can install things into the "C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI" folder.  Probably, the easiest solution is for the user to make that folder writeable to all users.  Then, the package should be able to install files there, even if VIPM is running as a non-admin user -- this is better than trying to run VIPM as Administrator, which can result in other issues.

[Anton Sundqvist]

Hi Jim, 

Thanks for helping out, this explains the issue.

Do you know if it would be a common issue? I’m considering if it would make sense to break out the cli features to a separate package if it causes problems.

Thanks, Anton

[Jim Kring]

Hi @Anton Sundqvist

Yes, this will be a common problem for users of your package.  By default the LabVIEW CLI folder will not be writable to users.

-Jim

[Anton Sundqvist]

Thanks for the input. I have now split the package in two to improve the user experience.

Thanks again for quick and accurate response. 
 

/Anton