On 22/01/25 6:52 pm, Simon Josefsson wrote: > I'm also curious about this. My approach has been to prefer "p+l" > (combined) when the binary package are more likely to be relevant as a > interactively used end-user tool (such as 'podman', 'skopep, 'cosign' > etc) and prefer "l+p" (both) when the binary packages are less likely to > be relevant as interactive end-user tools (such as build tools like > protoc plugins).
This is absolutely right. I suppose you'd follow almost the same philosophy for source packages (with multiple binary packages) outside of the go team as well? The same rule applies here. Best, Nilesh
