en Copyright 2025 Java http://opengrok.net:8080/history/src/release/packages/ucl/README#014647a30ff4c76a99962ee6b079db0d9cdf5949 packages: Add some missing dependencies* at requires cron, since atrun is started by cron and won't work without it, and also requires runtime because at runs jobs under /bin/sh.* bluetooth requires ppp for rfcomm_pppd (a very common use case).* bsdconfig and bsdinstall are written in shell script and therefore require /bin/sh.* devd requires /bin/sh to invoke its hooks.While here, document the policy for adding dependencies in the README.This will hopefully ensure we end up with consistent dependencies.MFC after: 1 dayReviewed by: baptDifferential Revision: https://reviews.freebsd.org/D52699 List of files: /src/release/packages/ucl/README Wed, 24 Sep 2025 18:39:35 +0000 Lexi Winter <ivy@FreeBSD.org> http://opengrok.net:8080/history/src/release/packages/ucl/README#66f36c3686762d9a6e48b0453fc7221be36a0eb8 packages: Add meta-package setsAdd several metapackages which contain no files themselves, but dependon other packages. This allows the user to install a system by usinga set like "FreeBSD-set-minimal" instead of having to know whichspecific packages are required, and it means if we add more packagein the future, existing installations will get them automatically aslong as they were installed using a set.The defined sets are significantly less granular than the actualpackages; the assumption is that users who want a very specific set ofpackages installed can do that manually, while sets are intended morefor typical users who just want to install FreeBSD.The following sets are defined:* minimal: the set of packages required to boot the system and bring up a multi-user UNIX system. This includes hardware support, networking (wireless, DHCP), basic functionality like syslogd, cron and periodic. It does not include a kernel, because the kernels are quite large and the user might want to use a custom kernel. sendmail and DMA are not included in minimal. Since we provide two MTAs, the user should select which one they want, or install one from ports. sshd is not included because it's not required for the base system, and the user might want to install it from ports. Some other significant subsystems (e.g. NFS, Kerberos) are also not included. The minimal set does not include any libraries itself, since we rely on dependencies to pull these in. This implies it doesn't include library manpages, which is fine, since users won't want manpages for libraries unless they've also installed the development packages.* devel: the compiler toolchain for building software, along with all "-dev" packages which include header files and static libraries.* lib32: 32-bit compatibility packages. This includes both runtime and development packages.* kernels: the kernel packages. For freebsd.org builds, this will be GENERIC, GENERIC-DEBUG, etc., for custom builds it will be whatever was set in $KERNCONF.* base: everything else; this includes the entire base system.For each set, also generate a <setname>-dbg set containing the debugpackages for the set.The sets are built along with the rest of the packages using a newscript called create-sets.sh, which examines the "set" annotation ineach package and puts it in the appropriate set. This is inanticipation of the later "groups" feature appearing in pkg itself, atwhich point we can simply replace the set annotation with the group.MFC after: 3 daysReviewed by: imp, baptDifferential Revision: https://reviews.freebsd.org/D52412 List of files: /src/release/packages/ucl/README Fri, 12 Sep 2025 20:59:25 +0000 Lexi Winter <ivy@FreeBSD.org> http://opengrok.net:8080/history/src/release/packages/ucl/README#014647a30ff4c76a99962ee6b079db0d9cdf5949 packages: Add some missing dependencies* at requires cron, since atrun is started by cron and won't work without it, and also requires runtime because at runs jobs under /bin/sh.* bluetooth requires ppp for rfcomm_pppd (a very common use case).* bsdconfig and bsdinstall are written in shell script and therefore require /bin/sh.* devd requires /bin/sh to invoke its hooks.While here, document the policy for adding dependencies in the README.This will hopefully ensure we end up with consistent dependencies.MFC after: 1 dayReviewed by: baptDifferential Revision: https://reviews.freebsd.org/D52699 List of files: /src/release/packages/ucl/README Wed, 24 Sep 2025 18:39:35 +0000 Lexi Winter <ivy@FreeBSD.org> http://opengrok.net:8080/history/src/release/packages/ucl/README#66f36c3686762d9a6e48b0453fc7221be36a0eb8 packages: Add meta-package setsAdd several metapackages which contain no files themselves, but dependon other packages. This allows the user to install a system by usinga set like "FreeBSD-set-minimal" instead of having to know whichspecific packages are required, and it means if we add more packagein the future, existing installations will get them automatically aslong as they were installed using a set.The defined sets are significantly less granular than the actualpackages; the assumption is that users who want a very specific set ofpackages installed can do that manually, while sets are intended morefor typical users who just want to install FreeBSD.The following sets are defined:* minimal: the set of packages required to boot the system and bring up a multi-user UNIX system. This includes hardware support, networking (wireless, DHCP), basic functionality like syslogd, cron and periodic. It does not include a kernel, because the kernels are quite large and the user might want to use a custom kernel. sendmail and DMA are not included in minimal. Since we provide two MTAs, the user should select which one they want, or install one from ports. sshd is not included because it's not required for the base system, and the user might want to install it from ports. Some other significant subsystems (e.g. NFS, Kerberos) are also not included. The minimal set does not include any libraries itself, since we rely on dependencies to pull these in. This implies it doesn't include library manpages, which is fine, since users won't want manpages for libraries unless they've also installed the development packages.* devel: the compiler toolchain for building software, along with all "-dev" packages which include header files and static libraries.* lib32: 32-bit compatibility packages. This includes both runtime and development packages.* kernels: the kernel packages. For freebsd.org builds, this will be GENERIC, GENERIC-DEBUG, etc., for custom builds it will be whatever was set in $KERNCONF.* base: everything else; this includes the entire base system.For each set, also generate a <setname>-dbg set containing the debugpackages for the set.The sets are built along with the rest of the packages using a newscript called create-sets.sh, which examines the "set" annotation ineach package and puts it in the appropriate set. This is inanticipation of the later "groups" feature appearing in pkg itself, atwhich point we can simply replace the set annotation with the group.MFC after: 3 daysReviewed by: imp, baptDifferential Revision: https://reviews.freebsd.org/D52412 List of files: /src/release/packages/ucl/README Fri, 12 Sep 2025 20:59:25 +0000 Lexi Winter <ivy@FreeBSD.org> http://opengrok.net:8080/history/src/release/packages/ucl/README#014647a30ff4c76a99962ee6b079db0d9cdf5949 packages: Add some missing dependencies* at requires cron, since atrun is started by cron and won't work without it, and also requires runtime because at runs jobs under /bin/sh.* bluetooth requires ppp for rfcomm_pppd (a very common use case).* bsdconfig and bsdinstall are written in shell script and therefore require /bin/sh.* devd requires /bin/sh to invoke its hooks.While here, document the policy for adding dependencies in the README.This will hopefully ensure we end up with consistent dependencies.MFC after: 1 dayReviewed by: baptDifferential Revision: https://reviews.freebsd.org/D52699 List of files: /src/release/packages/ucl/README Wed, 24 Sep 2025 18:39:35 +0000 Lexi Winter <ivy@FreeBSD.org> http://opengrok.net:8080/history/src/release/packages/ucl/README#66f36c3686762d9a6e48b0453fc7221be36a0eb8 packages: Add meta-package setsAdd several metapackages which contain no files themselves, but dependon other packages. This allows the user to install a system by usinga set like "FreeBSD-set-minimal" instead of having to know whichspecific packages are required, and it means if we add more packagein the future, existing installations will get them automatically aslong as they were installed using a set.The defined sets are significantly less granular than the actualpackages; the assumption is that users who want a very specific set ofpackages installed can do that manually, while sets are intended morefor typical users who just want to install FreeBSD.The following sets are defined:* minimal: the set of packages required to boot the system and bring up a multi-user UNIX system. This includes hardware support, networking (wireless, DHCP), basic functionality like syslogd, cron and periodic. It does not include a kernel, because the kernels are quite large and the user might want to use a custom kernel. sendmail and DMA are not included in minimal. Since we provide two MTAs, the user should select which one they want, or install one from ports. sshd is not included because it's not required for the base system, and the user might want to install it from ports. Some other significant subsystems (e.g. NFS, Kerberos) are also not included. The minimal set does not include any libraries itself, since we rely on dependencies to pull these in. This implies it doesn't include library manpages, which is fine, since users won't want manpages for libraries unless they've also installed the development packages.* devel: the compiler toolchain for building software, along with all "-dev" packages which include header files and static libraries.* lib32: 32-bit compatibility packages. This includes both runtime and development packages.* kernels: the kernel packages. For freebsd.org builds, this will be GENERIC, GENERIC-DEBUG, etc., for custom builds it will be whatever was set in $KERNCONF.* base: everything else; this includes the entire base system.For each set, also generate a <setname>-dbg set containing the debugpackages for the set.The sets are built along with the rest of the packages using a newscript called create-sets.sh, which examines the "set" annotation ineach package and puts it in the appropriate set. This is inanticipation of the later "groups" feature appearing in pkg itself, atwhich point we can simply replace the set annotation with the group.MFC after: 3 daysReviewed by: imp, baptDifferential Revision: https://reviews.freebsd.org/D52412 List of files: /src/release/packages/ucl/README Fri, 12 Sep 2025 20:59:25 +0000 Lexi Winter <ivy@FreeBSD.org>