I’d like to propose adding a bins option to the spm backend so users can restrict which executable products are built and linked.

Right now, when a Swift package exposes multiple executable products, mise appears to build and link all of them. In some cases, that means executables intended only for testing or internal use are also installed into bin and added to PATH.

A concrete example is swiftlang/swiftly:

• swiftly
• test-swiftly

    products: [
        .executable(
            name: "swiftly",
            targets: ["Swiftly"]
        ),
        .executable(
            name: "test-swiftly",
            targets: ["TestSwiftly"]
        ),
    ],

https://github.com/swiftlang/swiftly/blob/c4dc2419106bfc02ea0c698632e8dbee6d7c53e7/Package.swift#L14-L23

In normal usage, I only want swiftly. I do not want test-swiftly to be built or linked into PATH.

A config like this would solve the issue cleanly:

[tools]
"spm:swiftlang/swiftly" = { version = "latest", bins = ["swiftly"] }

Expected behavior:

• when bins is not set, keep the current behavior for backward compatibility
• when bins is set, only the listed executable products are built and linked
• if a listed name does not match an executable product, return a clear error

This seems preferable to filtering only at the symlink step, because it would also avoid unnecessary builds.

If this direction makes sense, I’d be happy to work on a PR.