On 2026-10-26 17:54, Daniel Engberg wrote:
...
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:
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.
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.
So far, multiple people have told you you're doing it wrong.
Please revert your changes.
I'm not sure if you don't read or don't understand, it's been marked
broken for month*s.
*https://cgit.freebsd.org/ports/commit/?id=d0528bbc1318371bfb9f81b3c1a4e56eeaab6c60
I missed that, sorry.
I only checked x11/budgie (which was the first one moved) and this was
NOT marked as broken.
Others aren't marked as broken as well.
Still I vote for setting an expiration date of at least 4 weeks in the
future before removal and after being flagged as broken for a reasonable
amount of time (especially for such a huge removal as in this case,
where many individual ports are affected as well as build infra scripts).
