• Why? git: 6ea8a98a6540 - main - x11/budgie: Remove from tree

    From Harry Schmalzbauer@freebsd@omnilan.de to muc.lists.freebsd.ports on Mon Oct 26 10:07:34 2026
    From Newsgroup: muc.lists.freebsd.ports

    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.

    People might fix budgie-desktop themself and simply don't have time to
    report upstream?
    Maybe others haven't had time yet to try it out yet and contribute
    fixes? They'll never get back to this if they miss this removal commit!

    "moving" (deleting) a port should _always_ require a maintainer timeout
    or maintainer approval.
    Nobody most be allowed to remove someone else's ports without plausible justification - which is either maintainer approval/request, maintainer-timeout, security-risk (plus maybe other's which don't come
    to my mind right now, but for sure not simply because 'does not build flawlessly' - if it's broken, mark it broken; only.)


    Best,
    -harry


    ---
    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(-)



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Tomek CEDRO@tomek@cedro.info to muc.lists.freebsd.ports on Mon Oct 26 10:57:23 2026
    From Newsgroup: muc.lists.freebsd.ports

    --000000000000dac2d8065ebb5b19
    Content-Type: text/plain; charset="UTF-8"

    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

    --000000000000dac2d8065ebb5b19
    Content-Type: text/html; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    <div dir=3D"auto"><div dir=3D"auto">On Mon, Oct 26, 2026, 10:20 Daniel Engb= erg &lt;<a href=3D"mailto:diizzy@freebsd.org">diizzy@freebsd.org</a>&gt; wr= ote:</div><div class=3D"gmail_quote gmail_quote_container" dir=3D"auto"><bl= ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef= t:1px solid rgb(204,204,204);padding-left:1ex">The tree is not intended as =
    a pile for broken ports. Feel tree to import <br>
    it in your overlay and keep it there, it&#39;s been listed as broken for 5+=

    months and no one has even raised a PR about it missing or trying to fix it= .<br>

    See also, <br>
    <a href=3D"https://docs.freebsd.org/en/books/porters-handbook/book/#dads-de= precated" rel=3D"noreferrer noreferrer" target=3D"_blank">https://docs.free= bsd.org/en/books/porters-handbook/book/#dads-deprecated</a><br>

    Best regards,<br>
    Daniel<br>

    On 2026-10-26 10:07, Harry Schmalzbauer wrote:<br>
    &gt;&gt; he branch main has been updated by diizzy:<br>
    &gt;&gt;<br>
    &gt;&gt; URL:<a href=3D"https://cgit.FreeBSD.org/ports/commit/" rel=3D"nore= ferrer noreferrer" target=3D"_blank">https://cgit.FreeBSD.org/ports/commit/= </a>? <br>
    &gt;&gt; id=3D6ea8a98a6540238635dd56b9ebecf3f3bacdeed6<br>
    &gt;&gt;<br>
    &gt;&gt; commit 6ea8a98a6540238635dd56b9ebecf3f3bacdeed6<br>
    &gt;&gt; Author:=C2=A0=C2=A0=C2=A0=C2=A0 Daniel Engberg&lt;diizzy@FreeBSD.o= rg&gt;<br>
    &gt;&gt; AuthorDate: 2026-10-26 05:40:44 +0000<br>
    &gt;&gt; Commit:=C2=A0=C2=A0=C2=A0=C2=A0 Daniel Engberg&lt;diizzy@FreeBSD.o= rg&gt;<br>
    &gt;&gt; CommitDate: 2026-10-26 06:34:32 +0000<br>
    &gt;&gt;<br>
    &gt;&gt; =C2=A0=C2=A0=C2=A0=C2=A0 x11/budgie: Remove from tree<br>
    &gt;&gt; =C2=A0=C2=A0=C2=A0=C2=A0 Broken for more than 5 months in tree wit= hout any PRs submitted<br>
    &gt;&gt; =C2=A0=C2=A0=C2=A0=C2=A0 Removes Budgie desktop and related ports<=

    &gt; <br>
    &gt; <br>
    &gt; I&#39;d like to strongly express that I think this is not a proper way=
    to <br>
    &gt; manage the FreeBSD port tree in this case (especially in this case, no=
    t <br>
    &gt; only though...).</blockquote></div><div dir=3D"auto"><br></div><div di= r=3D"auto"><div dir=3D"auto">Why do rough? I guess this port could be resur= rected and maintained by Harry right? :-)</div><div dir=3D"auto"><br></div>= <div dir=3D"auto">--</div><div dir=3D"auto">CeDeROM, SQ7MHZ, <a href=3D"htt= p://www.tomek.cedro.info">http://www.tomek.cedro.info</a></div></div><div c= lass=3D"gmail_quote gmail_quote_container" dir=3D"auto"></div></div>

    --000000000000dac2d8065ebb5b19--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ronald Klop@ronald-lists@klop.ws to muc.lists.freebsd.ports on Mon Oct 26 12:00:53 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_1787_1940997879.1793012453395
    Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit

    Van: Tomek CEDRO <tomek@cedro.info>
    Datum: maandag, 26 oktober 2026 10:57
    Aan: Daniel Engberg <diizzy@freebsd.org>, Harry Schmalzbauer <freebsd@omnilan.de>
    CC: dev-commits-ports-all@freebsd.org, freebsd-ports <freebsd-ports@freebsd.org>, Olivier Duchateau <duchateau.olivier@gmail.com>
    Onderwerp: Re: Why? git: 6ea8a98a6540 - main - x11/budgie: Remove from tree

    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



    Everything is still in git. If somebody wants Budgie back, it is possible to get it from git history, make it compiling/working again and create a PR. "Remove" sounds a bit more definitive than it actually is with source control.

    Ronald.

    ------=_Part_1787_1940997879.1793012453395
    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <br />
    <p><strong>Van:</strong> Tomek CEDRO &lt;tomek@cedro.info&gt;<br /> <strong>Datum:</strong> maandag, 26 oktober 2026 10:57<br /> <strong>Aan:</strong> Daniel Engberg &lt;diizzy@freebsd.org&gt;, Harry Schm= alzbauer &lt;freebsd@omnilan.de&gt;<br />
    <strong>CC:</strong> dev-commits-ports-all@freebsd.org, freebsd-ports &lt;f= reebsd-ports@freebsd.org&gt;, Olivier Duchateau &lt;duchateau.olivier@gmail= .com&gt;<br />
    <strong>Onderwerp:</strong> Re: Why? git: 6ea8a98a6540 - main - x11/budgie:=
    Remove from tree</p>

    <blockquote style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5p=
    x; border-left: #000000 2px solid; margin-right: 0px">
    <div class=3D"MessageRFC822Viewer" id=3D"P">
    <div class=3D"MultipartAlternativeViewer">
    <div class=3D"TextHTMLViewer" id=3D"P.P.P">
    <div>
    <div>On Mon, Oct 26, 2026, 10:20 Daniel Engberg &lt;<a href=3D"mailto:diizz= y@freebsd.org">diizzy@freebsd.org</a>&gt; wrote:</div>

    <div class=3D"gmail_quote gmail_quote_container">
    <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-= left:1px solid rgb(204,204,204);padding-left:1ex">The tree is not intended =
    as a pile for broken ports. Feel tree to import<br />
    it in your overlay and keep it there, it's been listed as broken for 5+<br =

    months and no one has even raised a PR about it missing or trying to fix it= .<br />
    <br />
    See also,<br />
    <a href=3D"https://docs.freebsd.org/en/books/porters-handbook/book/#dads-de= precated" target=3D"_blank">https://docs.freebsd.org/en/books/porters-handb= ook/book/#dads-deprecated</a><br />
    <br />
    Best regards,<br />
    Daniel<br />
    <br />
    On 2026-10-26 10:07, Harry Schmalzbauer wrote:<br />
    &gt;&gt; he branch main has been updated by diizzy:<br />
    &gt;&gt;<br />
    &gt;&gt; URL:<a href=3D"https://cgit.FreeBSD.org/ports/commit/" target=3D"_= blank">https://cgit.FreeBSD.org/ports/commit/</a>?<br />
    &gt;&gt; id=3D6ea8a98a6540238635dd56b9ebecf3f3bacdeed6<br />
    &gt;&gt;<br />
    &gt;&gt; commit 6ea8a98a6540238635dd56b9ebecf3f3bacdeed6<br />
    &gt;&gt; Author:&nbsp;&nbsp;&nbsp;&nbsp; Daniel Engberg&lt;diizzy@FreeBSD.o= rg&gt;<br />
    &gt;&gt; AuthorDate: 2026-10-26 05:40:44 +0000<br />
    &gt;&gt; Commit:&nbsp;&nbsp;&nbsp;&nbsp; Daniel Engberg&lt;diizzy@FreeBSD.o= rg&gt;<br />
    &gt;&gt; CommitDate: 2026-10-26 06:34:32 +0000<br />
    &gt;&gt;<br />
    &gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp; x11/budgie: Remove from tree<br />
    &gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp; Broken for more than 5 months in tree wit= hout any PRs submitted<br />
    &gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp; Removes Budgie desktop and related ports<=
    br />
    &gt;<br />
    &gt;<br />
    &gt; I'd like to strongly express that I think this is not a proper way to<=
    br />
    &gt; manage the FreeBSD port tree in this case (especially in this case, no= t<br />
    &gt; only though...).</blockquote>
    </div>

    <div>=C2=A0</div>

    <div>
    <div>Why do rough? I guess this port could be resurrected and maintained by=
    Harry right? :-)</div>

    <div>=C2=A0</div>

    <div>--</div>

    <div>CeDeROM, SQ7MHZ, <a href=3D"http://www.tomek.cedro.info">http://www.to= mek.cedro.info</a></div>
    </div>

    <div class=3D"gmail_quote gmail_quote_container">=C2=A0</div>
    </div>
    </div>
    </div>
    </div>
    </blockquote>
    <br />
    <br />
    Everything is still in git. If somebody wants Budgie back, it is possible t=
    o get it from git history, make it compiling/working again and create a PR.=
    "Remove" sounds a bit more definitive than it actually is with source cont= rol.<br />
    <br />
    Ronald.<br />
    =C2=A0
    ------=_Part_1787_1940997879.1793012453395--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Langille@dan@langille.org to muc.lists.freebsd.ports on Mon Oct 26 07:41:07 2026
    From Newsgroup: muc.lists.freebsd.ports

    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.
    --
    Dan Langille
    dan@langille.org


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Daniel Engberg@diizzy@FreeBSD.org to muc.lists.freebsd.ports on Mon Oct 26 12:44:22 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 2026-10-26 12:41, Dan Langille wrote:
    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.


    According to what?

    Best regards,
    Daniel


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thierry Thomas@thierry@freebsd.org to muc.lists.freebsd.ports on Mon Oct 26 14:38:33 2026
    From Newsgroup: muc.lists.freebsd.ports

    --V1Xr5A/8rqyt45v4
    Content-Type: text/plain; charset=iso-8859-1
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    Le lun. 26 oct. 26 =E0 12:44:22 +0100, Daniel Engberg <diizzy@FreeBSD.org>
    =E9crivait=A0:

    x11/budgie: Remove from tree
    Broken for more than 5 months in tree without any PRs submitt=
    ed
    Removes 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=
    ot
    only though...).
    =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.
    =20
    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=
    me
    time, before nuking this port.
    =20
    Agreed.
    =20
    =20
    According to what?

    According to common sense and the respect of the users.

    No need of a written policy fot that.
    --=20
    Th. Thomas.

    --V1Xr5A/8rqyt45v4
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iQJPBAEBCAA5FiEE5Ta+hThTmdALb6p28cUWs8g1l1MFAmrfV84bFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwzAAoJEPHFFrPINZdTOt4P+wXw5N2P4/xdUUC9YAuF 9snOMj+2fknzXznQkH+VLIMC1tPhn6QuaqLtlmqKRk9Kxz5VOTlwI6XSF3ueffaU Wrg34wHo3EoUWh5vgSQpvmbPnt0f2tmOZYdUzIdtsgeFYwL6ZFJBq+BFf6KFoKS6 +IEBljwm6n09cfPZb24XFQfYvpuMsn/BGp2cwbzScUIU6Gi2mDmUwXZwEtKyCSCd 6aqJwpBOMVS/RTsqih0gwgGNexAyfVnoAHBI3qG7aa4A0OFjVd7TXcn/M3WRTQsQ lQ+j8WECvAu7cTCBxPBU7LBXQpmGGBLzhjpUSQeihXWQW1EnUfQBD4111xr1FiLa Qph9FS+y+5c9ihRGq1r5KqvwvFXR4FINujX9mxmQ/ubSfM5UfxeP1WIOx/8zIiO4 rMKCx+oVAXvl23I9r1bTDG6FVF8Uxk29vGUyKg9lmTP3LGJrIcA4fh29UeSa7k+s h0PL1aUxNGtVarCAK7UX2iWtCyNTu5fq8GtfpubRj4n1G6ra7T6HWpb2kSPpokE3 aFFbs/p7qtdXWY6/3KxKgM9fAuB8cq34Szdrkxde54zdityagorECMNFxYOcFlMc X9/pkyVIm8cqvZJLPBWlpoqPF7vhoIxLsWNosMOo8XqTZCht6Dw4K1GJ4fHsrNEh codZL2J6maUE5rqQNYnCZVNh
    =XWyb
    -----END PGP SIGNATURE-----

    --V1Xr5A/8rqyt45v4--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Langille@dan@langille.org to muc.lists.freebsd.ports on Mon Oct 26 10:39:25 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Mon, Oct 26, 2026, at 10:22, Daniel Engberg wrote:
    On 2026-10-26 14:38, Thierry Thomas wrote:
    Le lun. 26 oct. 26 |a 12:44:22 +0100, Daniel Engberg <diizzy@FreeBSD.org>
    |-crivait-a:

    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.

    According to what?
    According to common sense and the respect of the users.

    No need of a written policy fot that.
    There is a policy, I've already linked to it again since you don't
    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."
    Also follow the policy here for process for broken/deprecated:
    rCi https://docs.freebsd.org/en/books/porters-handbook/porting-dads/#dads-noinstall-variables
    It has been broken for more than 5 months, there are no package(s) and
    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.
    Please follow procedure.
    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.
    rCi
    Your approach completely bypasses the bult-in mechanisms for users of a broken port.
    Maybe they built it and it was working, and did not update, and when they update,
    it's silently gone. The approach taken is not what we do.
    rCi
    So far, multiple people have told you you're doing it wrong.
    Please revert your changes.
    --
    Dan Langille - with portmgr hat
    dan@langille.org
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lexi Winter@ivy@freebsd.org to muc.lists.freebsd.ports on Mon Oct 26 14:44:09 2026
    From Newsgroup: muc.lists.freebsd.ports

    --RHK3q8pbkDs1Zn9Q
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline

    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.

    --RHK3q8pbkDs1Zn9Q
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iJEEABYKADkWIQSyjTg96lp3RifySyn1nT63mIK/YAUCat9nNhsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDMACgkQ9Z0+t5iCv2DAygEA6D/vfyM7Pboe6QKpkc7m BahxZXik/t2whazqzzKh3PcA/0T9TGmMQNg61p6s3IRwz9wm5/YLPk0H9VXdZQ17
    sEoF
    =7IcR
    -----END PGP SIGNATURE-----

    --RHK3q8pbkDs1Zn9Q--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.ports on Mon Oct 26 08:32:54 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 10/26/26 07:44, Lexi Winter wrote:
    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.

    (Not that I care about the specific port but I'm curious about the process:)

    Can a potential maintainer that is not a committer reinstate the port on
    their own?

    If not, it would seem that the thing missing for reinstatement would be
    someone requesting the reinstatement that also indicates they want to be
    the maintainer.

    If it does not already have such, I wonder if the policy should have
    some words about that for long-broken ports that are deleted.


    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.
    --
    ===
    Mark Millard
    marklmi at yahoo.com


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kurt Jaeger@pi@freebsd.org to muc.lists.freebsd.ports on Mon Oct 26 16:35:50 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi!

    Can a potential maintainer that is not a committer reinstate the port on their own?

    As usual: They submit a PR, and some committer will commit the update.
    --
    pi@FreeBSD.org +49 171 3101372 Now what ?


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lexi Winter@ivy@freebsd.org to muc.lists.freebsd.ports on Mon Oct 26 16:30:32 2026
    From Newsgroup: muc.lists.freebsd.ports

    --klKzMd1zIDqTbg6j
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    Harry Schmalzbauer wrote in <738be22b-2a6e-40ae-8c0e-9046b73cb73f@omnilan.d= e>:
    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?

    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.

    --klKzMd1zIDqTbg6j
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iJEEABYKADkWIQSyjTg96lp3RifySyn1nT63mIK/YAUCat+AJRsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDMACgkQ9Z0+t5iCv2DX8AEA3dKxl4gaMOexe6v2kFjG zRQqNG1xLBmozW2Qh802ewYBALGUd7h6X25cqi+woegBiaKapBSf/2ZQoHLSnulX
    jYYL
    =6HIl
    -----END PGP SIGNATURE-----

    --klKzMd1zIDqTbg6j--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Tomoaki AOKI@junchoon@dec.sakura.ne.jp to muc.lists.freebsd.ports on Tue Oct 27 04:01:11 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Mon, 26 Oct 2026 16:30:32 +0000
    Lexi Winter <ivy@freebsd.org> wrote:

    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.

    Maintainers are natural human. So situations like below can
    always happen.

    *The maintainer was urgently taken to hospital with some reason
    like traffic accident and kept 6 months without Internet access.

    *Luckily back to home and see the maintainer's ports is/are
    removed without marking as BROKEN, then marked DEPRECATED.

    How the maintainer feels?

    I think this is the enough reason to always take described
    steps before removal.


    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.

    The first post by Harry should be indicating the fact. Isn't it?


    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.

    Agreed with this specific point.

    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.

    Some limited fractures of them "could" post to forums.freebsd.org
    "Why is pkg want to remove ***?!", but it can be overlooked.

    Posts (toots / tweets) to SNS would more easier NOT to be noticed
    by devs.

    And unfortunately, registering at bugs.freebsd.org as a user seems
    NOT as straightforward as when I've registered, as of spammers.
    Newbies could be stuck there and simply resign with filing a PR.

    So, following steps and warn users via pkg (8) on each
    upgrade runs could give more chances for potential users
    to notice the situation with BROKEN/DEPRECATED messages.
    Isn't it?

    Regards.
    --
    Tomoaki AOKI <junchoon@dec.sakura.ne.jp>


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steve Kargl@kargls@comcast.net to muc.lists.freebsd.ports on Mon Oct 26 12:09:12 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 10/26/26 11:57, Daniel Engberg wrote:
    On 2026-10-26 19:49, Steve Kargl wrote:
    On 10/26/26 11:43, Daniel Engberg wrote:
    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

    Seems like there was a space added by accident in the url https://cgit.freebsd.org/ports/commit/? id=d0528bbc1318371bfb9f81b3c1a4e56eeaab6c60
    It is still missing DEPRECATED and EXPIRATION_DATE.

    Here's the patch you meant to commit instead of removing
    the port

    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= duchateau.olivier@gmail.com
    COMMENT= Modern and familiar desktop environment
    WWW= https://github.com/BuddiesOfBudgie/budgie-desktop

    -BROKEN= Fails to build, vapigen command fails
    +DEPRECATED= Fails to build, vapigen command fails
    +EXPIRATION_DATE = 2016-11-26

    LICENSE= GPLv2 LGPL21
    LICENSE_COMB= multi

    HTH
    --
    steve


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Langille@dan@langille.org to muc.lists.freebsd.ports on Mon Oct 26 17:41:06 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Mon, Oct 26, 2026, at 17:23, Thierry Thomas wrote:
    Le lun. 26 oct. 26 |a 22:06:05 +0100, Jochen Neumeister <joneum@FreeBSD.org>
    |-crivait-a:

    I have restored the ports and resolved the problem.
    The commit: https://cgit.freebsd.org/ports/commit/?id=ec0f0d269bc36f04fb0c1409ca38d3e6bcc6d4f3
    --
    Dan Langille
    dan@langille.org
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mathieu Arnold@mat@freebsd.org to muc.lists.freebsd.ports on Tue Oct 27 07:30:25 2026
    From Newsgroup: muc.lists.freebsd.ports


    --bhqdnu4uhpgwpt6f
    Content-Type: text/plain; charset=iso-8859-1
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    On Mon, Oct 26, 2026 at 09:24:07PM +0100, Daniel Engberg wrote:
    On 2026-10-26 20:09, Steve Kargl wrote:
    On 10/26/26 11:57, Daniel Engberg wrote:
    On 2026-10-26 19:49, Steve Kargl wrote:
    On 10/26/26 11:43, Daniel Engberg wrote:
    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
    Seems like there was a space added by accident in the url https://cgit.freebsd.org/ports/commit/? id=3Dd0528bbc1318371bfb9f81b3c1a4e56eeaab6c60
    It is still missing DEPRECATED and EXPIRATION_DATE.
    =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=
    dgie/budgie-desktop
    =20
    -BROKEN=3D=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Fails to build,=
    vapigen command fails
    +DEPRECATED=3D=A0=A0=A0 Fails to build, vapigen command fails +EXPIRATION_DATE =3D 2016-11-26
    =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
    =20
    No, it's not. The port is broken so your suggested patch is wrong. The re=
    st
    makes no sense given it hasn't been available for 5+ months (once again).

    Daniel,

    That is true. That patch should keep the BROKEN line. This is not a
    problem. Anyone can see that and keep the line.

    Your personal preferences on how ports go away are only that. They are
    not policy.

    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.

    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.

    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.

    This is important. The ports tree is not a playground for committers. It
    exists so that users can use software.

    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.

    In the future, please follow that procedure.

    --=20
    Mathieu Arnold

    --bhqdnu4uhpgwpt6f
    Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQITBAABCgB9FiEE9XJBpJetWizkEBUef2IOCp6dQb4FAmrgRQBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 NzI0MUE0OTdBRDVBMkNFNDEwMTUxRTdGNjIwRTBBOUU5RDQxQkUACgkQf2IOCp6d Qb5gyAv+OVaqqfIRSf42VGg1aKzqTwbBzuXN6lijGx7SA0p4YcnBFmxWZQlCTWb6 s/4HIUvkyUvjgXawDdlwEK0nHR6sX+RrpPCcOy5a/d4lNfrzYk6YefOyYlcn0wjp VJ+0LhZIvuMRzxNM9j976zA6tPoAJDqvq+zMLsQ+Lwz7LeGlFLrSOBCAo6Ve5zuv 5X3jOdGKdfDGEGQNjxQpRGtzAqn1Lyb+A+cpnfTj/qQL1MYfPiBpoMwm1AQI1D3k AEBp8FwzKkioOTK0x9G10VNRPEKjBGkDNgdv5AXzadUPSH8CS+iG415tKMBStHMt nHHrALFLOm+Ix0fJBld7/vdzRHHLg2XxuKYfVoi/qY75WhAb9niMK4Zu+r6AaXl1 FWCSrPKTpfSfipVIbIOJxWfhYg6gXWi6n4NM5++FpFufrr/I/2F5IYkQjR/z+Alg 71183f621P+Kn0sqDF6iIvR9ZylSLYHPcz+XMogMFXgsJDCJx0KkNvXhgo3gCCJC
    G0IvoBXq
    =JNrB
    -----END PGP SIGNATURE-----

    --bhqdnu4uhpgwpt6f--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mathieu Arnold@mat@freebsd.org to muc.lists.freebsd.ports on Tue Oct 27 19:17:35 2026
    From Newsgroup: muc.lists.freebsd.ports


    --hwawzs4yd37xvvjz
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    On Tue, Oct 27, 2026 at 09:42:55AM +0100, Daniel Engberg wrote:
    On 2026-10-27 07:30, Mathieu Arnold wrote:
    Daniel,
    =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
    =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=
    gs.
    Since there's a discrepancy which several have recognized there's already=
    a
    discussion taking place and hopefully document it in the end.

    Daniel,

    I wrote the policy above.

    If you do not understand it, please tell me which part you do not understan=
    d.

    If you refuse to follow it, please do not remove ports.

    Kind regards,

    --=20
    Mathieu Arnold

    --hwawzs4yd37xvvjz
    Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQITBAABCgB9FiEE9XJBpJetWizkEBUef2IOCp6dQb4FAmrg6r5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 NzI0MUE0OTdBRDVBMkNFNDEwMTUxRTdGNjIwRTBBOUU5RDQxQkUACgkQf2IOCp6d Qb5rBwwAv+fGimRnSn55na6Jsyfd0EAd20noyn0ytOmfr2clDikEDlJt1HiNXMbB 0moePDpb6zPdc12MtlCAGeqep/oYB5+aAtZvcTVEgO7wTKWqifp7y3PeridJOJwB 4VIAMcml0dDX7BIoWe9RAl42H8k+EtxXCWtywBdNx3SqonV1tWtmvh9hqIrMNqt+ rC/Nl9/BPtwxfNC0pXUmm0aHwka1rrlLLZa5az2jFa04E57b6zqE2F7RLvqKQ3gx c6HLSbC5JJS0OqMWCwtXd7x6Dy0S1Pxe9J6fDFKteUYl+8F3EZJjp7JtT6u3QCoo v2Dc2flmZ3QY0FjAZEzCi3q8XpK9A1vSBD7FJsKXCPavMSsvEFYAjSUwWHux1Rjl LOHoml8Y9NviYyFCs5sZjskQolSfnFnLQdqWLeIzXbkhnZe4jdcmNHlsijhoQbBu OuQUbbGS3OIRlDi3GAN3lRf9SS2Ub/DUBHg/uTmz3v5a1ag5YWdNBunIfcyIzyYb
    fAiC7WLt
    =3ziB
    -----END PGP SIGNATURE-----

    --hwawzs4yd37xvvjz--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lexi Winter@ivy@freebsd.org to muc.lists.freebsd.ports on Wed Oct 28 12:38:10 2026
    From Newsgroup: muc.lists.freebsd.ports

    --b6WzzMvCvnGBW/5Z
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    Tomoaki AOKI wrote in <20261027040111.131ababec8ff680f9b6ae451@dec.sakura.n= e.jp>:
    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?

    if a maintainer is urgently taken to hospital for five months and cannot maintain their port, of course i feel empathy for them as a person. we
    can hope that in the mean time, someone else will step up and maintain
    the port.

    but this does not change the mechanical/policy decisions. if a port is unmaintained, it doesn't matter why it's unmaintained.

    if no one else steps up to maintain the port, and the port is removed,
    the previous maintainer upon returning home may recurrect the port and
    become the maintainer against, since the entire history of the port is available in the Git history.

    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.
    =20
    clearly these theoretical users do not actually exist.
    =20
    The first post by Harry should be indicating the fact. Isn't it?
    =20
    if so, this was not clear to me. i thought Harry is objecting on behalf
    of theoretical users.

    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.

    okay, but this doesn't prevent us removing the port. the effect is the
    same either way: the port does not appear in built package tree.

    --b6WzzMvCvnGBW/5Z
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iJEEABYKADkWIQSyjTg96lp3RifySyn1nT63mIK/YAUCauHsrxsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDMACgkQ9Z0+t5iCv2B4yQEA0G7ruFhHf1Utwdg8MsDm qyMSJEYsxJE7/2JEek+h4J8BAO3i/8D9GMvEjsNSi4+QB3O8j1nJrFCZUnb5str6
    qSwG
    =/Q/N
    -----END PGP SIGNATURE-----

    --b6WzzMvCvnGBW/5Z--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2