On 31/5/2024 21:22, Sergio Had wrote:
Otherwise we get this: https://github.com/macports/macports-ports/commit/6e2c1e19a4ffce5d59a9cdf8147022ad176dffed <https://github.com/macports/macports-ports/commit/6e2c1e19a4ffce5d59a9cdf8147022ad176dffed>While LimeChat has existed for 4 years in MacPorts: https://github.com/macports/macports-ports/commits/8c30b0e9fd88d94c115b38c92809b909c4eac9aa/aqua/LimeChat/Portfile <https://github.com/macports/macports-ports/commits/8c30b0e9fd88d94c115b38c92809b909c4eac9aa/aqua/LimeChat/Portfile>And now two conflicting ports for the same thing.
I greatly doubt that this (or any other addition of a duplicate port) was deliberate, so having a specific rule against it wouldn't have changed anything. Yes, it's a problem that needs to be fixed.
- Josh
