Hi! 👋 An semi-aesthetic semi-practical question: is the period-separated path (like

<http://some.path.to|some.path.to>.pex.binary

) under

dist/

configuarble to be

/

-separated instead? The practicality comes from the fact that we share bazel and pants repos in one codebase and it would be nice for use to refer to the results of the different builds using a unified way. Thank you!

Generally, targets that output into

dist/

have an

output_path

field to allow you to customize the name of the output.

That is per target, though, and you must provide the full path manually then. There’s currently no way to use

/

for the default generated output_path value: https://github.com/pantsbuild/pants/blob/79140750fa921bcc1d51722d2c161cc5236911bd/src/python/pants/core/goals/package.py#L63-L76 https://www.pantsbuild.org/docs/reference-pex_binary#codeoutput_pathcode

There's probably a way to use a new field or target and a union rule to write a plugin that changes this behavior for built-in goals like

package

Re the plugin suggestion, generally something like that could work but, here, I unfortunately don't think it would. Each

package

rule (e.g.

pex_binary

) hardcodes where to output the file, which is usually based on the

output_path

field @acceptable-football-32760 one idea is to add an option

[package].output_path_default_use_slashes

or something like that..I think we'd consider that. Although I'm hesitant because it's relatively niche and we try to think in general about "options fatigue". Wdyt?

there are good reasons to use slash separated: filesystem name lengths, for one. so any option in this direction would actually make a good default at some point.

Thanks a lot for the consideration! I admit it is indeed niche so I was thinking of making some emi-hacky plugin about it (along the lines of @flat-zoo-31952 s) suggestion

It's not niche... I agree with @witty-crayon-22786 that slashes should probably be the default.