he branch main has been updated by diizzy:
URL:https://cgit.FreeBSD.org/ports/commit/? id=6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
commit 6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
Author: Daniel Engberg<diizzy@FreeBSD.org>
AuthorDate: 2026-10-26 05:40:44 +0000
Commit: Daniel Engberg<diizzy@FreeBSD.org>
CommitDate: 2026-10-26 06:34:32 +0000
x11/budgie: Remove from tree
Broken for more than 5 months in tree without any PRs submitted
Removes Budgie desktop and related ports
---
MOVED | 7 +
Mk/Uses/budgie.mk | 84 --
deskutils/Makefile | 1 -
deskutils/budgie-desktop-view/Makefile | 25 -
deskutils/budgie-desktop-view/distinfo | 5 -
.../files/patch-src_budgie__desktop__view.vala | 15 -
.../files/patch-src_file__item.vala | 38 -
deskutils/budgie-desktop-view/pkg-descr | 4 -
deskutils/budgie-desktop-view/pkg-plist | 26 -
sysutils/Makefile | 1 -
sysutils/budgie-control-center/Makefile | 50 --
sysutils/budgie-control-center/distinfo | 3 -
.../budgie-control-center/files/patch-meson.build | 22 -
...h-panels_info-overview_cc-info-overview-panel.c | 70 --
...-panels_info-overview_cc-info-overview-panel.ui | 24 -
.../files/patch-panels_meson.build | 23 -
.../files/patch-panels_power_cc-power-panel.c | 27 -
.../files/patch-panels_printers_pp-host.c | 11 -
.../patch-panels_user-accounts_cc-realm-manager.c | 22 -
.../files/patch-panels_user-accounts_meson.build | 12 -
.../files/patch-shell_cc-panel-loader.c | 22 -
.../files/patch-shell_meson.build | 12 -
sysutils/budgie-control-center/pkg-descr | 4 -
sysutils/budgie-control-center/pkg-plist | 207 -----
x11-themes/Makefile | 1 -
x11-themes/budgie-backgrounds/Makefile | 19 -
x11-themes/budgie-backgrounds/distinfo | 3 -
x11-themes/budgie-backgrounds/pkg-descr | 2 -
x11-themes/budgie-backgrounds/pkg-plist | 19 -
x11/Makefile | 4 -
x11/budgie-desktop/Makefile | 101 ---
x11/budgie-desktop/distinfo | 3 -
...ddiesofbudgie-default-settings.gschema.override | 32 -
.../files/patch-data_budgie-portals.conf | 7 -
x11/budgie-desktop/files/patch-data_meson.build | 15 -
x11/budgie-desktop/files/patch-meson.build | 23 -
.../files/patch-src_appindexer_Application.vala | 29 -
.../files/patch-src_appindexer_meson.build | 12 -
.../files/patch-src_daemon_bsd_meson.build | 11 -
...rc_daemon_bsd_plugins_power_gsd-power-manager.c | 60 --
.../files/patch-src_dialogs_power_dbus.vala | 11 -
.../files/patch-src_dialogs_power_window.vala | 23 -
...src_panel_applets_budgie-menu_OverlayMenus.vala | 11 -
...h-src_panel_applets_budgie-menu_UserButton.vala | 11 -
.../patch-src_panel_applets_clock_ClockApplet.vala | 13 -
...applets_user-indicator_UserIndicatorWindow.vala | 34 -
.../patch-src_panel_settings_settings__raven.vala | 11 -
.../files/patch-src_session_meson.build | 24 -
...wm_20__solus-project.budgie.wm.gschema.override | 18 -
x11/budgie-desktop/files/patch-src_wm_wm.vala | 32 -
.../patch-update-libxfce4windowing-vapi.patch | 893 ---------------------
x11/budgie-desktop/pkg-descr | 9 -
x11/budgie-desktop/pkg-plist | 240 ------
x11/budgie-screensaver/Makefile | 42 -
x11/budgie-screensaver/distinfo | 3 -
x11/budgie-screensaver/files/budgie-screensaver.in | 7 -
.../files/patch-data_meson.build | 13 -
x11/budgie-screensaver/files/patch-meson.build | 33 -
.../files/patch-src_gnome-screensaver.c | 11 -
.../files/patch-src_gs-auth-pam.c | 12 -
x11/budgie-screensaver/pkg-descr | 3 -
x11/budgie-screensaver/pkg-plist | 98 ---
x11/budgie-session/Makefile | 32 -
x11/budgie-session/distinfo | 3 -
.../files/patch-gnome-session_gsm-app.c | 18 -
x11/budgie-session/pkg-descr | 2 -
x11/budgie-session/pkg-plist | 125 ---
x11/budgie/Makefile | 36 -
x11/budgie/files/pkg-message.in | 16 -
x11/budgie/files/xprofile.in | 79 --
x11/budgie/pkg-descr | 3 -
x11/budgie/pkg-plist | 1 -
72 files changed, 7 insertions(+), 2916 deletions(-)
The tree is not intended as a pile for broken ports. Feel tree to import
it in your overlay and keep it there, it's been listed as broken for 5+ months and no one has even raised a PR about it missing or trying to fix
it.
See also, https://docs.freebsd.org/en/books/porters-handbook/book/#dads-deprecated
Best regards,
Daniel
On 2026-10-26 10:07, Harry Schmalzbauer wrote:
he branch main has been updated by diizzy:
URL:https://cgit.FreeBSD.org/ports/commit/?
id=6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
commit 6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
Author: Daniel Engberg<diizzy@FreeBSD.org>
AuthorDate: 2026-10-26 05:40:44 +0000
Commit: Daniel Engberg<diizzy@FreeBSD.org>
CommitDate: 2026-10-26 06:34:32 +0000
x11/budgie: Remove from tree
Broken for more than 5 months in tree without any PRs submitted
Removes Budgie desktop and related ports
I'd like to strongly express that I think this is not a proper way to manage the FreeBSD port tree in this case (especially in this case, not only though...).
On Mon, Oct 26, 2026, 10:20 Daniel Engberg <diizzy@freebsd.org> wrote:
The tree is not intended as a pile for broken ports. Feel tree to import
it in your overlay and keep it there, it's been listed as broken for 5+
months and no one has even raised a PR about it missing or trying to fix it. >>
See also,
https://docs.freebsd.org/en/books/porters-handbook/book/#dads-deprecated
Best regards,
Daniel
On 2026-10-26 10:07, Harry Schmalzbauer wrote:
he branch main has been updated by diizzy:
URL:https://cgit.FreeBSD.org/ports/commit/?
id=6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
commit 6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
Author: Daniel Engberg<diizzy@FreeBSD.org>
AuthorDate: 2026-10-26 05:40:44 +0000
Commit: Daniel Engberg<diizzy@FreeBSD.org>
CommitDate: 2026-10-26 06:34:32 +0000
x11/budgie: Remove from tree
Broken for more than 5 months in tree without any PRs submitted
Removes Budgie desktop and related ports
I'd like to strongly express that I think this is not a proper way to
manage the FreeBSD port tree in this case (especially in this case, not
only though...).>
Why do rough? I guess this port could be resurrected and maintained by Harry right? :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
he branch main has been updated by diizzy:
URL:https://cgit.FreeBSD.org/ports/commit/?
id=6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
commit 6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
Author: Daniel Engberg<diizzy@FreeBSD.org>
AuthorDate: 2026-10-26 05:40:44 +0000
Commit: Daniel Engberg<diizzy@FreeBSD.org>
CommitDate: 2026-10-26 06:34:32 +0000
x11/budgie: Remove from tree
Broken for more than 5 months in tree without any PRs submitted
Removes Budgie desktop and related ports
I'd like to strongly express that I think this is not a proper way to
manage the FreeBSD port tree in this case (especially in this case, not
only though...).
To my understanding there's the BROKEN flag available in the ports framework, which perfectly matches here and should have been set as a
first measure.
If for some unknown reason removing other's work makes live easier for
ports tree people@freeebsd, mark it for removal (deprecate) at the same time, before nuking this port.
On Mon, Oct 26, 2026, at 05:07, Harry Schmalzbauer wrote:
he branch main has been updated by diizzy:
URL:https://cgit.FreeBSD.org/ports/commit/?
id=6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
commit 6ea8a98a6540238635dd56b9ebecf3f3bacdeed6
Author: Daniel Engberg<diizzy@FreeBSD.org>
AuthorDate: 2026-10-26 05:40:44 +0000
Commit: Daniel Engberg<diizzy@FreeBSD.org>
CommitDate: 2026-10-26 06:34:32 +0000
x11/budgie: Remove from tree
Broken for more than 5 months in tree without any PRs submitted
Removes Budgie desktop and related ports
I'd like to strongly express that I think this is not a proper way to
manage the FreeBSD port tree in this case (especially in this case, not
only though...).
To my understanding there's the BROKEN flag available in the ports
framework, which perfectly matches here and should have been set as a
first measure.
You are correct. It should not have been removed the way it was.
It should be put back and marked BROKEN.
If for some unknown reason removing other's work makes live easier for
ports tree people@freeebsd, mark it for removal (deprecate) at the same
time, before nuking this port.
Agreed.
edx11/budgie: Remove from tree
Broken for more than 5 months in tree without any PRs submitt=
otRemoves Budgie desktop and related ports=20
=20
I'd like to strongly express that I think this is not a proper way to manage the FreeBSD port tree in this case (especially in this case, n=
meonly though...).=20
=20
To my understanding there's the BROKEN flag available in the ports framework, which perfectly matches here and should have been set as a first measure.
You are correct. It should not have been removed the way it was.
=20
It should be put back and marked BROKEN.
=20
If for some unknown reason removing other's work makes live easier for ports tree people@freeebsd, mark it for removal (deprecate) at the sa=
=20time, before nuking this port.=20
Agreed.
=20
According to what?
On 2026-10-26 14:38, Thierry Thomas wrote:Also follow the policy here for process for broken/deprecated:
Le lun. 26 oct. 26 |a 12:44:22 +0100, Daniel Engberg <diizzy@FreeBSD.org>There is a policy, I've already linked to it again since you don't
|-crivait-a:
According to common sense and the respect of the users.According to what?You are correct. It should not have been removed the way it was.x11/budgie: Remove from tree
Broken for more than 5 months in tree without any PRs submitted >>>>>> Removes Budgie desktop and related ports
I'd like to strongly express that I think this is not a proper way to >>>>> manage the FreeBSD port tree in this case (especially in this case, not >>>>> only though...).
To my understanding there's the BROKEN flag available in the ports
framework, which perfectly matches here and should have been set as a >>>>> first measure.
It should be put back and marked BROKEN.
If for some unknown reason removing other's work makes live easier for >>>>> ports tree people@freeebsd, mark it for removal (deprecate) at the same >>>>> time, before nuking this port.Agreed.
No need of a written policy fot that.
appear to not be aware. https://docs.freebsd.org/en/books/porters-handbook/book/#dads-deprecated "Permanently broken ports will be removed from the tree entirely."
It has been broken for more than 5 months, there are no package(s) andPlease follow procedure.
no PR(s) about fixing it or it being missing including quarterly so what users are you referring to? Additionally as Roland pointed you can fix
it, use old port as base and update it if you're attached to it.
You are short-cutting the process. First, mark the port broken after
one month of it being actually broken. Did you do that? No. A few
months later, mark it deprecated. Did you do that? No. With those
steps taken, the port will be garbage collected by the usual process.
No need for you to delete it like you did.
Dan Langille wrote in <2936739a-9bff-4fd5-9cb6-c6eff3662a3e@app.fastmail.com>:
You are short-cutting the process. First, mark the port broken after
one month of it being actually broken. Did you do that? No. A few
months later, mark it deprecated. Did you do that? No. With those
steps taken, the port will be garbage collected by the usual process.
No need for you to delete it like you did.
it's been broken for five months. who cares? if the answer is anything other than "no one", the person who cares can resurrect the port and
maintain it.
otherwise, nothing is lost by deleting a broken port.--
we should not let arbitrary rules stand in the way of improving the
ports tree, especially considering the state of ports.
Can a potential maintainer that is not a committer reinstate the port on their own?
On 2026-10-26 15:44, Lexi Winter wrote:
it's been broken for five months. who cares? if the answer is anything other than "no one", the person who cares can resurrect the port and maintain it.[...]
=20
Is there really an improvement for the ports tree after this removal?
From a users point of view, I consider almost any removal as loss, not as=an
improvement.
Somebody put significant efforts into providing this port.
Hiding from user visible surface doesn't improve anything imho.
Further cleanup should require approval by the maintainer imho.
If (former) maintainer doesn't respond within a reasonable timeframe
(like 8 weeks maybe) set expiration date (another 4 weeks).
People have another chance to notice about it and maybe adopt it.
This tiny bureaucracy is justified by the resulting transparency in my opinion.
Harry Schmalzbauer wrote in <738be22b-2a6e-40ae-8c0e-9046b73cb73f@omnilan.de>:
On 2026-10-26 15:44, Lexi Winter wrote:
it's been broken for five months. who cares? if the answer is anything other than "no one", the person who cares can resurrect the port and maintain it.[...]
Is there really an improvement for the ports tree after this removal?
yes: we used to have a port that didn't build. now we don't have a port
that doesn't build. the quality of the ports tree has improved.
From a users point of view, I consider almost any removal as loss, not as an
improvement.
what did you lose? the port doesn't build.
Somebody put significant efforts into providing this port.
someone put a lot of effort into porting 4.3BSD to the Tahoe, but we
don't ship that in FreeBSD, because it's obsolete.
Hiding from user visible surface doesn't improve anything imho.
no one is hiding anything, anyone can see the Git history.
Further cleanup should require approval by the maintainer imho.
what maintainer? the port has been broken for five months. it is
clearly not maintained.
If (former) maintainer doesn't respond within a reasonable timeframe
(like 8 weeks maybe) set expiration date (another 4 weeks).
it's been five months. that's far longer than your proposed timeline.
People have another chance to notice about it and maybe adopt it.
if people are really using this port, they would have noticed that it
cannot be built, and they would have fixed it -- if they cared.
clearly these theoretical users do not actually exist.
This tiny bureaucracy is justified by the resulting transparency in my opinion.
the real bureaucracy is being unable to improve the ports tree due to objections on behalf of users who don't actually exist.
On 2026-10-26 19:49, Steve Kargl wrote:It is still missing DEPRECATED and EXPIRATION_DATE.
On 10/26/26 11:43, Daniel Engberg wrote:Seems like there was a space added by accident in the url https://cgit.freebsd.org/ports/commit/? id=d0528bbc1318371bfb9f81b3c1a4e56eeaab6c60
Try again, https://cgit.freebsd.org/ports/commit/?
id=d0528bbc1318371bfb9f81b3c1a4e56eeaab6c60
(I have no dog in this fight except the long email thread cluttering
my inbox.)
d0528bbc seems to be missing
DEPRECATED= "Port has been broken for 5 months"
EXPIRATION_DATE=2026-11-30
Le lun. 26 oct. 26 |a 22:06:05 +0100, Jochen Neumeister <joneum@FreeBSD.org>The commit: https://cgit.freebsd.org/ports/commit/?id=ec0f0d269bc36f04fb0c1409ca38d3e6bcc6d4f3
|-crivait-a:
I have restored the ports and resolved the problem.
On 2026-10-26 20:09, Steve Kargl wrote:dgie/budgie-desktop
On 10/26/26 11:57, Daniel Engberg wrote:
On 2026-10-26 19:49, Steve Kargl wrote:It is still missing DEPRECATED and EXPIRATION_DATE.
On 10/26/26 11:43, Daniel Engberg wrote:Seems like there was a space added by accident in the url https://cgit.freebsd.org/ports/commit/? id=3Dd0528bbc1318371bfb9f81b3c1a4e56eeaab6c60
Try again, https://cgit.freebsd.org/ports/commit/? id=3Dd0528bbc1318371bfb9f81b3c1a4e56eeaab6c60=20
=20
(I have no dog in this fight except the long email thread cluttering
my inbox.)
=20
d0528bbc seems to be missing
=20
DEPRECATED=3D "Port has been broken for 5 months" EXPIRATION_DATE=3D2026-11-30
=20
=20
Here's the patch you meant to commit instead of removing
the port
=20
diff --git a/x11/budgie-desktop/Makefile b/x11/budgie-desktop/Makefile index 539584dfdc2e..722e89b949fe 100644
--- a/x11/budgie-desktop/Makefile
+++ b/x11/budgie-desktop/Makefile
@@ -9,7 +9,8 @@ MAINTAINER=3D=A0=A0=A0=A0 duchateau.olivier@gmail.com
=A0COMMENT=3D=A0=A0=A0=A0=A0=A0 Modern and familiar desktop environment
=A0WWW=3D=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 https://github.com/BuddiesOfBu=
vapigen command fails=20
-BROKEN=3D=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Fails to build,=
st+DEPRECATED=3D=A0=A0=A0 Fails to build, vapigen command fails +EXPIRATION_DATE =3D 2016-11-26=20
=20
=A0LICENSE=3D=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 GPLv2 LGPL21
=A0LICENSE_COMB=3D=A0=A0=A0=A0=A0=A0=A0=A0=A0 multi
=20
HTH
=20
No, it's not. The port is broken so your suggested patch is wrong. The re=
makes no sense given it hasn't been available for 5+ months (once again).
On 2026-10-27 07:30, Mathieu Arnold wrote:gs.
Daniel,=20
=20
That is true. That patch should keep the BROKEN line. This is not a problem. Anyone can see that and keep the line.
=20
Your personal preferences on how ports go away are only that. They are
not policy.
=20
The long-standing policy is that ports that do not build get marked
BROKEN. This has two effects. First, the build clusters stop trying to build ports that cannot finish. Second, the mark shows that the port is broken. People who care about the port can then look at it.
=20
After a while, a port marked BROKEN gets a DEPRECATED reason and an EXPIRATION_DATE. The date is usually a few months in the future. The
change also needs a PORTREVISION bump. All of this must be merged to the quarterly branch.
=20
This shows that the port will be removed in the future, and why. The
reason is in DEPRECATED. For ports that build, users see a notice when
they upgrade. The notice says the port is deprecated and will go away.
=20
This is important. The ports tree is not a playground for committers. It exists so that users can use software.
=20
Your commit removed six ports. Only one of them had a BROKEN tag. You should have added DEPRECATED and EXPIRATION_DATE to the broken port. You should also have set those variables on all ports that depend on that broken port. Then all of them would be marked for deletion.
=20
In the future, please follow that procedure.
=20
It's not documented in either Porters Handbook or in the new policies as
such and there are conflicting messages, logical and practical shortcomin=
Since there's a discrepancy which several have recognized there's already=a
discussion taking place and hopefully document it in the end.
Maintainers are natural human. So situations like below can
always happen.
=20
*The maintainer was urgently taken to hospital with some reason
like traffic accident and kept 6 months without Internet access.
=20
*Luckily back to home and see the maintainer's ports is/are
removed without marking as BROKEN, then marked DEPRECATED.
=20
How the maintainer feels?
=20if people are really using this port, they would have noticed that it cannot be built, and they would have fixed it -- if they cared.=20
=20
clearly these theoretical users do not actually exist.
The first post by Harry should be indicating the fact. Isn't it?
But non-maintainer users may lock the pkg (if they know it's
possible and how-to) if pkg(8) attempt to delete it as there's
no built pkg in the repo and forget about it unless already-installed
one still work for them. They unlikely to "officially" report.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 60:37:02 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,219 |