5/7/2023 0 Comments Uninstall macforge![]() For example, to process the BOM file for the Sample.pkg receipt, type the following statement at the Terminal prompt. To use the lsbom tool, simply pass the path to the BOM file as its input. Its counterpart is the mkbom tool, which creates a BOM file for a given directory. The tool is a standard addition to the BSD subsystem of MacOS X. It then outputs the text to another file, or to stdout by default. The lsbom tool takes a BOM file as its input and renders its contents into human readable text. To read its contents, use the command-line tool lsbom to preprocess the BOM file. It is also a binary format and, as a result, is not directly readable. The BOM file format has its origins in the NeXTStep operating system. This file is present in both the installer package and receipts bundle. ![]() It also defines the locations of each file on the target volume. The BOM file is a list of all the files that comprise the software payload. Without the right receipt to guide it, an installer for a new product version may be unable to upgrade the current product correctly. But removing a receipt, without removing the product, creates a new problem. This is often done to reclaim extra space, especially when the product associated with the receipt no longer exists. There are software tools that purge the contents of the Receipts directory. Also missing are the two aliases to that file from the Resources subdirectory.įigure 1. paz.gz file containing the actual payload. Notice that the bundle has most of the same files as an installer package. It also tells the installer package if the latter has to do an upgrade, as opposed to an installation.įigure 1 shows the internal structure of a typical receipt bundle. Its presence indicates that a product has been installed successfully. The copy of the installer package is known as a receipt bundle. ![]() The path to this directory is /Library/Receipts on the boot volume. The Receipts BundleĪfter the Installer installs a software payload, it creates a copy of the package in the Receipts directory. A copy of this project can be obtained at the following URL. To get readers started on their own uninstallers, the Xcode project Uninstall is made available for downloading. This article will demonstrate how to use AppleScript Studio to build an uninstaller. In these situations, an uninstaller tool can be useful. As a result, removing Xcode from the system can be a laborious process. The installer also stores files in other directories such as /System/Library and /Library/Application Support. Its installer creates the custom directory Developer to contain its files. A good example of such a product is Xcode. ![]() Others will create custom directories to store the files. But some products will have multiple files installed in different directories. In fact, most products are easy to remove - they are contained in a single folder, and trashing that folder completely uninstalls the product. This feature is sadly missing from PackageMaker, though not without reason. Third-party tools such as ViseX and InstallerMaker can add an uninstall option to their installers. But the one thing we were unable to do with the tool is to build an uninstaller. We also learned how to localize that package for different languages, and how to customize it with scripts. In a previous MacTech article, we learned how to use the PackageMaker tool to build a distribution package. Educational Institution and Student DiscountsĬolumn Tag: Scripting Uninstalling with AppleScriptīuilding an uninstaller with AppleScript Studio.
0 Comments
Leave a Reply. |