Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Help me name some targets please:
• nfpm_rpm_package + nfpm_deb_package
• nfpm_rpm + nfpm_deb
• rpm_nfpm + deb_nfpm
• rpm_nfpm_package + deb_nfpm_package
I'm including `nfpm` because the packages built by nfpm will probably differ somewhat with packages built using the native tooling. `debian_package` for example uses debian native tooling like dpkg-deb.

Could it be `nfpm_package` with `packager="deb"` etc?

How much does the user care that `nfpm` package is different than the native tooling package? Enough that this needs to be expressed in the target?

For example, `lambdex` creates Lambdas from pexes, so they are slightly different than ones you'd create by hand, but we don't call that out in the target type, which is `python_awslambda`.

OTOH a `pex` is substantially different from any other way of packaging a python binary, in ways that the user probably does care about, so the target is `pex_binary`, not `python_binary`.

Ok. I guess this is too complex for quick/disjoint chat questions. I'll put together a Google doc later today.