Opened 3 years ago
Last modified 3 years ago
#63981 new enhancement
Avoid Breaking Changes
| Reported by: | ztroop (Zackary Troop) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: |
Description
This is a ticket around port release management improvements. I'd like to discuss some points raised in:
https://github.com/macports/macports-ports/commit/c4e8bb15818ee2f0debe47b8e9bf5b4574a61c09
Is there a way to revert this without causing another major disruption? This change has broken node14, wangle, watchman and all their dependants.
Our builds broke because node14 failed to install.
We knew that moving to openssl3 by default would expose some ports that would need pegging back to 1.1. This is not a surprise, or a problem. Just do it.
I think it's reasonable to have some expectation of stability around a popular package management tool. A casual attitude towards breakage is a little concerning to say the least. My question in this ticket, if we can anticipate a potential breakage... Can we not plan or coordinate fixes before negatively affecting users?
Discussion like this should happen, but should happen on the macports-dev mailing list. Tickets are not for discussion; they are for concrete actionable bug reports and feature requests.