3 ms·
That’s a per-application package, and the name is defined in the pkginfo(4) file. And contrary to your claim about SVR4 packaging being too cognitively difficul
by Annatar 9y ago
That’s a per-application package, and the name is defined in the pkginfo(4) file. And contrary to your claim about SVR4 packaging being too cognitively difficult to grasp, it is the simplest of all packaging subsystems to learn. IPS is far worse and the tooling to make an IPS package is truly lacking, especially when it comes to documentation, and then especially when it comes to configuration management with packages.
- cryptonector 9y agoWhy the bleeep should a package create a database, and name it something it wants, for me?! No! This is NOT OK.
- Annatar 9y agoBecause no changes to the system should be made in any other way than through operating system packages; that is what they are for. This minimizes dependencies and simplifies interfaces (two commands, pkgadd(1M) and pkgrm(1M) do everything). The database engineering department decides database names and creates the appropriate packages; that is no longer the decision of the system or database administrators to make. It is no longer their job and hasn’t been for at least a decade and a half.