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

Pants

Several targets need `files`  including `archive`, `makeself_archive`, and `relocated_files`. But, the files I need to package are owned by either `resources` or `python_sources`.

How can I use `resources` and `python_sources` targets as `files`?

There isn't an `experimental_wrap_as_files` target, and `experimental_wrap_as_resources` does not seem to be usable by `archive` and friends.

Does passing them through a `shell_command(command="true", dependencies=[...], output_directories=["."])` work? (ick, if it does, but at least it unblocks you?)

Just checking for bigger-picture/more-context: I imagine you've consider whether this is possible to do with a `pex_binary` in the chain somewhere, and let that handle arranging the sources and resources appropriately?

I'm looking to create an archive of a collection of (basically) python scripts and the yaml metadata files that describe those scripts. The organization of the files differs from how a virtualenv is constructed, so `pex_binary` seems like an even larger leap. I'll try `shell_command`.