nipkg get-dependencies Syntax

[Oli_Wachno]

Me again, sorry.....

after having been convinced I should do more CLI 😉 I have miserably failed today testng the get-dependencies command:

I have copied a nipkg file to a local repo folder and executed

nipkg get-dependencies "C:\Temp\NIPKG_Test\LocalRepositories\TestRepo\ni-webserver_20.6.0.49152-0+f0_windows_x64.nipkg:windows_all=20.6.0.49152-0+f0"

resulting in 

Error -125233: The specified packet 'C:\Temp\NIPKG_Test\LocalRepositories\TestRepo\ni-webserver_20.6.0.49152-0+f0_windows_x64.nipkg:windows_all=20.6.0.49152-0+f0' is invalid. Expected Syntax: 'Paket_Name[:Architektur][Version_Operatorversion]'

help for get-dependencies says:

 PACKAGE-SPECIFIERS
A space-separated list of packages for which dependencies should be
calculated.
Each package-specifier should follow the format:
<package_name>[:<architecture>][<version_operation><version>]
If using '<' or '>' in the <version_operation>, add quotation marks
around the package-specifier, or it will be read as a cmd I/O operation.
Example: "pkg-name:windows_all>=1.0.0.12345-0+f0"

so I tried 

nipkg get-dependencies "C:\Temp\NIPKG_Test\LocalRepositories\TestRepo\ni-webserver_20.6.0.49152-0+f0_windows_x64.nipkg:windows_all=20.6.0.49152-0+f0"

returning the same error.

Invoking list-fields like

nipkg list-fields "C:\Temp\NIPKG_Test\LocalRepositories\TestRepo\ni-webserver_20.6.0.49152-0+f0_windows_x64.nipkg" 

returns correct output, so the package should be ok.

Maybe I am not getting the concept of the get-dependencies command 

Any suggestions, what I am doing wrong?

[WesW · Accepted solution]

Tricky! The problem is that it's expecting the package name, and not the package filename.

nipkg.exe get-dependencies ni-webserver

ni-securityupdate-kb67l8lcqw-killbits   2.1.0.49152-0+f0        windows_all     This is an infrastructure package for NI Software.
ni-metauninstaller      20.0.0.49152-0+f0       windows_all     This package provides support for uninstallation of NI products.
ni-euladepot    20.0.0.49152-0+f0       windows_all     Installs license and notice files.
ni-mdfsupport   20.0.0.49152-0+f0       windows_all     This package installs the files necessary to support building deployments from NI's ADEs.
ni-msiproperties        20.0.0.49152-0+f0       windows_all     Installs the files necessary for Package Manager to resolve NI properties (e.g. the NI Program Files installation directory) and evaluate MSI conditions.
ni-msdotnet4x   4.6.3.49152-0+f0        windows_all     NI installer for Microsoft's .NET Framework 4.6.2
ni-msvcrt-2015  14.1.5.49152-0+f0       windows_all     NI installer for Microsoft Visual C++ 2015 Run-Time Update 3 (includes KB3118401)
ni-launcher     20.0.0.49152-0+f0       windows_all     NILauncher is for browsing and launching National Instruments software installed on your computer. Installs on Windows 8.x and newer.
ni-ssl-support  20.0.0.49152-0+f0       windows_all     NI SSL Support helps you enable Secure Sockets Layer (SSL) encryption on the Web Server.
ni-webserver    20.0.0.49152-0+f0       windows_x64     The NI Web Server hosts web applications and web UIs.

Some nipkg.exe commands only accept package names, but if they accept package filenames or paths, they will often say in the CLI help, like this for install:

nipkg.exe help install

install - Installs a package

nipkg install [OPTIONS]... PACKAGES...

   Install packages

   PACKAGES
      A list of all the packages to install.
      A package can be specified by its name or by its path. If a package name
      is specified, that name must exist in one of the configured feeds. If a
      package path is specified (a path to a file with a .nipkg extension), the
      contents of this file are passed to the install.

[Oli_Wachno]

Thanks  so much for your help!

Is my assumption right, that the specified package has to be member of a feed which is registered with NI Package manager? Speaking of get-dependencies.

[WesW]

---

@Oli_Wachno wrote:

...

Is my assumption right, that the specified package has to be member of a feed which is registered with NI Package manager? Speaking of get-dependencies.

---

Yes - it must be either in a registered feed, or a package that is already installed.