Spotfire SPK versioning

You create the file SpotfireSPK.spk containing the packages you want to distribute to others using the Spotfire Server. You might need to change or update the packages that you distribute, which requires changing the version of the Spotfire SPK.

After you create the SpotfireSPK.spk, you give it to Spotfire Server administrator, who places it in a distribution area on Spotfire Server. It is used to distribute packages to other analysts who are using Spotfire Analyst. If you create a package and distribute it using the Spotfire SPK mechanism, and you need to update the package code, you must create a new SpotfireSPK.spk

You can create or change a Spotfire SPK using TERR, as described in Creating the Spotfire package. The TERR function buildSPK creates the Spotfire SPK using the versioning rule details for the following tasks.
Note: The SPK property BuiltVersion is NOT the same as the package version. That information is stored in the package DESCRIPTION file. BuiltVersion is always specified as four components (N.n.n.n).

You can learn more about the TERR function buildSPK by reading its help file. See Obtaining the SpotfireSPK toolset for more information.

Task Rule details
Generating a new DCF If you generate a new DCF using writeLines or a text editor, and then you pass the new DCF to the buildSPK function, the function overwrites the old DCF, and the list contains only the packages you provide in the text argument of writeLines. The BuiltVersion is always set to 1.0.0.0.
Recreating a new DCF using the same version If you do not need to increment or keep the older DCF, you can simply regenerate it using writeLines. Creating a new DCF always sets BuiltVersion to 1.0.0.0 by default. However, if you use this method of generating the DCF, Spotfire Server does not register the package as a new one, so it does not distribute the package to the users.
Adding package names to an existing DCF If you only add packages to the existing DCF using a text editor, and then run the buildSPK function, passing in the edited DCF, the buildSPK function increments the BuiltVersion to a minor version number (for example, 1.1.0.0).
Removing package names from an existing DCF If you remove a package from the existing DCF using a text editor, and then run the buildSPK function, passing in the edited DCF, the buildSPK function increments the BuiltVersion to a major version number (for example, 2.0.0.0).
Assigning a specific version number to a DCF If you create a DCF and want to assign a specific version number to it, run the buildSPK function and pass in the DCF argument, along with the argument version, setting it to the version you want. This argument is a character string or a numeric_version object containing four components (for example, version = "1.2.3.4").