I'm think I'm missing the thinking on how this could make a package less portable. The idea I'm after is making it so that you have some swiftpm plugin commands automatically available, potentially ones that aren't "built into the toolchain" from a starting point.
The one-liner is
I wish I could type "swift package preview-documentation" right after cloning someone's package, and have that work without the Package.swift having an explicit dependency on swift-docc-plugin.
In case you're thinking I'm talking about the "I need this to compile the package dependencies", that's not my intent here. As it stands in the manifest of Package.swift, there isn't really a concept of the kind of dependency, and maybe that's part of the issue that I'm trying to detangle?