Editing Portal:FreeBSD,OpenBSD,etc (section)

=== DragonFly DPorts development process ===

DragonFly’s DPorts development process is interesting because it is explicitly derivative and automated. DragonFly documentation says the DPorts workflow uses three repositories: FreeBSD Ports, DeltaPorts, and DPorts. DeltaPorts is an overlay applied on top of FreeBSD Ports to create DPorts.<ref>DragonFly BSD, “DPorts Contributions,” https://www.dragonflybsd.org/docs/howtos/DPortsContributions/, accessed July 3, 2026.</ref>

The same documentation describes monthly syncs with FreeBSD Ports, transformation scripts, staged builds, build-status tracking, and failure-fixing. It also explains that users can help by testing ports, reporting bugs, checking pull requests, and fixing DPorts failures.<ref>DragonFly BSD, “DPorts Contributions,” https://www.dragonflybsd.org/docs/howtos/DPortsContributions/, accessed July 3, 2026.</ref>

For Perl, this means DragonFly benefits from FreeBSD’s Perl ports work but must still account for DragonFly-specific build and runtime differences. Perl itself and Perl modules come through the package system, but the DPorts layer may need local fixes when FreeBSD ports do not build cleanly on DragonFly.