macos-trash: Update to 2.0.0

[subpop]

Description

Type(s)

• update
• bugfix
• enhancement
• security fix

Tested on

macOS 26.0 25A354 arm64
Xcode 26.0 17A324

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@halostatue for port macos-trash.

[halostatue]

According to the release notes for v2, it should work with macOS 13 or later.

The test builds for 13 and 14 are failing; they should not fail. If the port advertises earlier versions of macOS, that should be updated.

I'm not in town to review this in more depth until October.

[ryandesign]

According to the release notes for v2, it should work with macOS 13 or later.

That may refer to being able to run on macOS 13 or later after being built on a newer version of macOS, but that's not how MacPorts works.

The test builds for 13 and 14 are failing

CI failure on macOS 13 is:

error: 'macos-trash-2.0.0': package 'macos-trash-2.0.0' is using Swift tools version 5.11.0 but the installed version is 5.8.1

And on macOS 14:

error: 'macos-trash-2.0.0': package 'macos-trash-2.0.0' is using Swift tools version 5.11.0 but the installed version is 5.10.0

[halostatue]

Understood. Part of what I'm asking—-and can't verify because I'm away from my computer for ten more days—is whether there's something upstream that is incorrect because it's using tools that aren't installed/installable on macOS 13 or 14, or whether those tools should be upgraded when building this tool, or if it should be declared 15+ only.

[CL-Jeremy]

Upstream declares macOS 10.13+, not 13+. Homebrew has already bumped minimum OS support to 14+ (Swift 6.0).

It's very typical for macOS programs to require higher toolchain versions for language support while the supported runtime system version baseline is lower. For C/C++ we have LLVM.org or GCC to help. For Swift we could attempt a Swift.org toolchain, but it's quite debatable as Apple won't support this usage on macOS, and oftentimes it's related to SDK availability. Unless it's solved, the best bet would be to get a binary directly (prabably extracting from a MacPorts/Homebrew prebuilt package will do) or build with Mint (as suggested by upstream) in a VM of a newer OS version.

[halostatue]

I'm fine with whatever decision is made as long as MacPorts will warn if it's tried on an unsupported system if we can't install the appropriate support version.