aiuto

Please no. Unless you want to write an extensive specification for how the two will merge and how they are sorted. E.g. what is the output order of "1", "11",...

Yup. `# do not sort` is a viable tool for people needing this. I was never a fan of buildifier sorting things by default. Lists of things belong in the...

The least surprising behavior is that all the top level pkg rules implement `stamp` as done in cc_binary. I consider that a minimal requirement. **stamp** - Integer; optional; default is...

Maybe we should start from needs for stamping, and then work back to features to achieve that. 1. We certainly need the default to be a repeatable constant value. This...

Status update: #288 is ready to go - it implements the `--stamp` flag and `stamp` attribute behavior of Bazel's `*_binary` rules - It gets the time stamp from the BUILD_TIMESTAMP...

It's a specific choice, but more on Bazel itself rather than rules_pkg. We need to predict file names during analysis, but we don't let you read the info file containing...

The fundamental bazel behavior is that no file reads other than ..bzl and BUILD files can impact the analysis phase, and that all action input and output files are defined...

You can make the renames in a .bzl file that you generate before the bazel build, then load that from BUILD files where you want to rename things.

No. I meant that a [--workspace_status_command](https://bazel.build/reference/command-line-reference#flag--workspace_status_command) script would generate status data and a .bzl file (in your source tree) that can be loaded by the BUILD file. Then you turn...

Sure. But what other choices do you have? Bazel doesn't make the time stamp accessible directly to Starlark at analysis time, so I can't get it into the file name....