Testing the division of the FreeBSD base system into packages

TrueOS Project объявил about testing experimental builds FreeBSD 12-STABLE и FreeBSD 13-CURRENT, in which a monolithic base system is converted into a set of interconnected packages. Assemblies evolve within the project pkgbase, which provides the means to use the native pkg package manager to manage the packages that make up the base system.

Delivery in the form of separate packages makes it possible to significantly simplify the process of updating the base system and use the single pkg utility both to update additional applications (ports) and to update the base system, including user-space components and the kernel. The project also makes it possible to smooth out the previously rigidly defined boundaries between the base system and the ports / package repository, and in the process of updating, take into account the compatibility of third-party programs with the components of the main environment and the kernel.

Pkgbase splits the base system into the following packages:

  • userland (meta package covering all packages with base system userland components)
  • userland-base (main binaries and libraries)
  • userland-docs (system manuals)
  • userland-debug (debug files placed in /usr/lib/debug)
  • userland-lib32 (libraries for compatibility with 32-bit applications);
  • userland-tests (testing frameworks)
  • kernel (main kernel in GENERIC configuration)
  • kernel-debug (kernel built in debug mode Witness)
  • kernel-symbols (debug symbols for the kernel, placed in /use/lib/debug)
  • kernel-debug-symbols (debug symbols, when building the kernel in Witness mode)

Additionally, several packages are provided for building from source: src (base system code installed in /usr/src), buildworld (file /usr/dist/world.txz with buildworld build log), buildkernel (file /usr/dist/kernel .txz with buildkernel build log) and buildkernel-debug (file /usr/dist/kernel-debug.txz with kernel build debug log).

Packages for the 13-CURRENT branch will be updated once a week, and for the 12-STABLE branch every 48 hours. If the default configuration files change, they are merged with local changes in the /etc directory during the update installation. If a conflict is identified that does not allow merging the settings, then the local version is left, and the proposed changes are saved in files with the extension ".pkgnew" for subsequent manual parsing (to list conflicting files with settings, you can use the command "find /etc | grep '.pkgnew $'").

Source: opennet.ru

Add a comment