FreeBSD ports frozen
For more than 48 hours now, no changes have been accepted or made to the tree, and here’s why.A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the ports tree in order to implement some clean up efforts. It turns out someone committed the entire github-copilot-cli Linux binary to ports, as part of the github-copilot-cli port. It’s not a “real” port because the tool isn’t open source and its license doesn’t allow for modifications.
- ▪For more than 48 hours now, no changes have been accepted or made to the tree, and here’s why.A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the port
- ▪It turns out someone committed the entire github-copilot-cli Linux binary to ports, as part of the github-copilot-cli port.
- ▪It’s not a “real” port because the tool isn’t open source and its license doesn’t allow for modifications.
Lobsters files mainly under programming. We currently carry 145 of its stories.
Opening excerpt (first ~120 words) tap to expand
Home > FreeBSD > FreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binaryFreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binary Thom Holwerda 2026-07-23 FreeBSD 2 CommentsA rather unusual announcement was made late last night: the FreeBSD project has frozen their ports repository. For more than 48 hours now, no changes have been accepted or made to the tree, and here’s why.A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the ports tree in order to implement some clean up efforts.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Osnews.