12 ms·
One package's app is another package's dependency, so this distinction cannot work in the general case.
by rlpb 2y ago
One package's app is another package's dependency, so this distinction cannot work in the general case.
- rcxdude 2y agoIt can work perfectly well, at least as far as API/ABI compatibility. An app is an executable, a library is a static or dynamic library. Something isn't generally both at once (a project or package might have a library and some tool applications related to the library, but those tend to get split out by distribution package maintainers anyway, and with cargo there's always a top-level package which sets the pinning, the rest are libraries whether or not they're the top level in other contexts). If you're talking about IPC or RPC, then yes, this matters more in terms of compatibility, but that's an area where a lot more attention is paid to compatibility in the first place, by everyone.