# FreeBSD 16 Completely Removes GPL Code FreeBSD 16 has eliminated the last GPL-licensed code from its base system. - **Source:** [Slashdot](https://brifing.si/source/0f34d58e-1ccd-45a6-ab82-2de4065dc7ad) - **Published:** 2026-07-15 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/939813fc-1cba-4662-9034-e3ea2a57f397 ## Major Change in FreeBSD 16 FreeBSD 16 has taken a significant step by removing the last GPL-licensed code from its base system. The old GNU 'dialog' implementation has been replaced with 'bsddialog'. This change marks the end of FreeBSD's GPL dependencies. ## Removal of GNU Subtree With FreeBSD 16, the GNU subtree has also been removed from the base system. This means FreeBSD no longer contains any GNU code. Developers believe this will enhance the system's independence. ## Change Process The process to remove GNU 'dialog' began in February and has now been integrated into the FreeBSD source tree. This change will be completed by the official release of FreeBSD 16.0. The community is closely following the process. ## FreeBSD 16.0 Release Date FreeBSD 16.0 is expected to be released in December 2027. This will be the first FreeBSD version completely free of GPL code. Developers continue to work on improving the stability and performance of the release. ## Community Response The open-source community has welcomed FreeBSD's decision to eliminate GPL code. This move is expected to enhance FreeBSD's independence and flexibility. The community eagerly awaits the new release. ## Future of FreeBSD FreeBSD 16 is a significant milestone for the project's future. Being completely free of GPL code will improve FreeBSD's license compliance and freedom. This step could also serve as an example for other open-source projects. ## Sources covering this story - https://bsd.slashdot.org/story/26/07/15/1727252/freebsd-16-retires-the-last-of-its-gpl-code?utm_source=rss1.0mainlinkanon&utm_medium=feed — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._