NI Package Manager (NIPM)
Where does NI Package Manager store its' feeds and attributes?
Solved!
You may already have discarded this possibility, but I think it isn't excluded by your description, so...
I suspect you can remove all the feeds you don't want (i.e. all the feeds?) using a combination of `feed-list` and `feed-remove` and the CLI for nipkg.exe.
You'll probably need some command-line text parsing, I got this "working" in Powershell...
nipkg feed-list | ForEach-Object { $n=$_.Split()[0]; if (-not [string]::IsNullOrEmpty($n)) { "$n" } }
This outputs the names of all feeds that are configured.
I expect (although I don't want to try on a real system right now... 😉 ) that you could add a bit to the end of this, something like (untested):
nipkg feed-list | ForEach-Object { $n=$_.Split()[0]; if (-not [string]::IsNullOrEmpty($n)) { nipkg feed-remove "$n" } }
Of course you could also do filtering in the if condition, or probably many other places (I'm not a Powershell expert...)
I can draft it in Bash or CMD if you prefer? 😉
More seriously, I think you might have some luck with your equivalent of
C:\Users\Christian\AppData\Local\National Instruments\NI Package Manager\nipkg.ini
Edit:
That seems to control some extra feeds, but the system feeds are added I think by the file:
C:\Program Files\National Instruments\NI Package Manager\Deployment\nipkg.ini
Running the Powershell to remove them did remove most cases (some wiggling required for those with spaces in the name) but they readded when I launched NIPM, so I think changing the ini above might be required.
After enjoying the opportunity to try some things
For the sake of documentation of who ever may read this 😉
.\nipkg feed-list | ForEach-Object { $n=$_.Split()[0]; if (-not [string]::IsNullOrEmpty($n)) { .\nipkg feed-remove "$n" } }
works, but you must not forget .\ before nipk.exe
Resulting in
After checking ni-package-manager-released.ini, my understanding is that NI Package Manager blocks the removal of its' own feed, which I regard to be a convenient safety feature.
The remaining errors basically state, that the feeds were not existing. Maybe these have been recursive calls to dependencies, which already had been removed.
Yet, I have been surprised, that invoking nikg.exe feed-list still returns a bunch of feeds. I suspect that these belong to the software packages already installed on my computer.
Can anyone confirm the statements above?
If you use the NIPM CLI (nipkg.exe) to add the feed, you can specify a "--system" flag to add the feed to the config for all users.
