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

Pants

the two compiles would both produce classpath entries, and would match the same subjects, but only one would contribute to the classpath for each subject

if you're interested in starting sketching out `@rule`s for this, it would be great to have.

i also wonder whether it would be possible to port classpath computation into the engine before compilation itself.

...but maybe not, because ivy is bootstrapping it.

I’ve been wanting to do that. I think that was the plan last year

<@U066LC126>: was having this conversation with <@U0AR45336> yesterday... i'm probably being a bit too aggressive as to how much will be ported in in order to remote compile. porting more than just individual process executions in (to move from ExecutionGraph based concurrency to engine concurrency) would involve a lot of output changes (ie: how do you report Rules running and processes being invoked... we're currently silent) and also this classpath stuff

not a _huge_ amount, and definitely separable... so maybe still feasible?

cc <@U054MQUPL> re the output change thing

Is looking for `pants.ini` the canonical way to find the root of a pants workspace?

in theory you can run without a config... in practice...

So a file names pants which is executable?

If I try to run `./pants list ::` without a pants.ini, I get an error

```
  File "/Users/dwagnerhall/src/github.com/pantsbuild/pants/src/python/pants/option/options_bootstrapper.py", line 102, in get_bootstrap_options
    pre_bootstrap_config = Config.load(configpaths)
  File "/Users/dwagnerhall/src/github.com/pantsbuild/pants/src/python/pants/option/config.py", line 57, in load
    with open(configpath, 'r') as ini:

Exception message: [Errno 2] No such file or directory: u'/Users/dwagnerhall/tmp/workspace/pants.ini'
```

well, i know that the reason for making the root the `pants` script was to support the "no config" usecase.

<@U6YPB4SJX>: i think you could do `./pants --config-files='[]' list ::`

but yea, i guess it will not work by default.

(I'm trying to work out what value to put in <https://github.com/bazelbuild/buildtools/blob/master/wspace/workspace.go#L30> for pants)

Is it an error to have a file named pants within your workspace?

no, but that would be a very good idea. because the search path for the `pants` file is from `cwd` and up

Ok, so if I teach buildozer the heuristic "traverse up until the first executable file named pants", we would be happy to add that restriction to pants?