Editing Portal:FreeBSD,OpenBSD,etc (section)

=== DragonFly BSD and DPorts ===

'''DragonFly BSD''' was forked from FreeBSD 4.8 and developed its own kernel and system architecture, especially around SMP, clustering ideas, and the HAMMER/HAMMER2 filesystems. Its third-party software model is based on '''DPorts'''.

DragonFly’s documentation says that DPorts is DragonFly’s own third-party software build system and that it is based on FreeBSD’s Ports Collection. The documentation adds that differences between FreeBSD ports and DPorts are intentionally kept to a minimum, both for familiarity and to leverage FreeBSD ports work.<ref>DragonFly BSD, “DPorts and pkg(8),” https://www.dragonflybsd.org/docs/howtos/DPortsUsage/, accessed July 3, 2026.</ref>

The same page says that DragonFly daily snapshots and releases starting with DragonFly 3.4 come with `pkg(8)` already installed, and that `pkg` is used as the binary package manager.<ref>DragonFly BSD, “DPorts and pkg(8),” https://www.dragonflybsd.org/docs/howtos/DPortsUsage/, accessed July 3, 2026.</ref>

The DragonFly DPorts repository describes DPorts as a derivative of FreeBSD’s Ports Collection. It says DPorts serves the same purpose for DragonFly that the Ports Collection serves for FreeBSD, and that products of DPorts are executable software manipulated by the `pkg(8)` binary package manager.<ref>DragonFly BSD, “DragonFlyBSD/DPorts,” GitHub, https://github.com/dragonflybsd/dports, accessed July 3, 2026.</ref>

Perl on DragonFly therefore follows the FreeBSD-like model more than the OpenBSD model. Perl is primarily a package/ports-managed language. Perl module packages follow the ports tradition, and Perl version changes are handled as part of the DPorts/pkg ecosystem rather than as a base-system language contract.