NI Package Manager (NIPM)

cancel
Showing results for 
Search instead for 
Did you mean: 

I want to uninstall a package and NOT uninstall its dependencies.

i'm trying to automate a build process where I have to programmatically install and uninstall packages during a hierarchical build. When calling "remove" there doesn't seem to be an option to remove ONLY a given package. NI Package manager will remove all dependencies as well if those dependencies are not used by another package on the system.

 

You may ask "why would you want the dependencies of a package to remain if the dependent package is removed and there are no other callers of a dependency package?"  That's a complicated answer, but for now just treat it as a requirement. I'm hoping there's an option to remove only the package I specifically say to remove and not remove the dependencies.

 

any help would be appreciated. 

0 Kudos
Message 1 of 5
(367 Views)

I would try looking into the lock operation for NIPKG Command Line Interface.

2019-08-26_09h28_18.png

__________________________________
Bill Eisenhower
Certified LabVIEW & TestStand Developer
0 Kudos
Message 2 of 5
(285 Views)

Hi Chris,

 


That's a complicated answer, but for now just treat it as a requirement.


I would be interested in hearing the complicated answer. If you don't want to post it here, let me now and we can set up a quick chat.

 

In general, we never want to leave a system in a broken state where package dependencies are left unsatisfied. That runs counter to the benefits that we are trying to achieve by moving to a packaged experience across the platform. That being said, I'm always interested in hearing more about our user's specific use cases to see how we can accommodate.

 

Thanks.

Aaron Peña

Product Owner, Package and License Management

National Instruments

0 Kudos
Message 3 of 5
(280 Views)

Hey Aaron,

I'm not sure how removing a dependent package but leaving dependencies in place breaks a system. There may be some confusion.  Here's a diagram of what I'm lookin for.

 

2019-08-29_20h02_56.png

 

In this case, Package B, C and D should NOT be broken. All of their dependencies are still satisfied.

0 Kudos
Message 4 of 5
(254 Views)
Highlighted

Hey Chris,

 

Ah okay. Apologies, I definitely misunderstood your original post. Thanks for the clarification.

 

I'll take a note and add this to our backlog. Could you also crosslink or create an idea for this in our new NI Package Management Idea Exchange?

 

Thanks.

- Aaron

Message 5 of 5
(231 Views)