PocketBuilder creates and uses PKG files to determine if any objects present on a source control server are missing from local PowerScript targets. Up-to-date PKG files insure that the latest objects in source control are available to all developers on a project, and that the objects are associated with a named PKL file.
Ideally, PKG files are not necessary. If the source control system exposes the latest additions of objects in a project through its SCC interface, PocketBuilder can obtain the list of all objects added to a project since the last status refresh. However, many source control systems do not support this, so PocketBuilder uses the PKG files to make sure it has an up-to-date list of objects under source control.
PKG files are registered and checked in to source control separately from all other objects in PocketBuilder. They are automatically updated to include new objects that are added to source control, but they can easily get out of sync when multiple users simultaneously register objects to (or delete objects from) the same source control project. For example, it is possible to add an object to source control successfully yet have the check-in of the PKG file fail because it is locked by another user.
You cannot see the PKG files in the System Tree or Library painter, unless you set the root for these views to the file system. To edit PKG files manually, you should check them out of source control using the source control manager and open them in a text editor. (If you are using PBNative, you can edit PKG files directly in the server storage location, without checking them out of source control.)
You can manually add objects to the PKG file for a PocketBuilder
library by including a new line for each object after the @begin
Objects line.
