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 point is that even recomputing the failures when the target hasn't changed is expensive

In which case I'd need to cache the error!

(new engine caches errors by default. time will tell whether that is the right decision)

(... the reason it might not be a good decision would be transient errors)

(... but those need their own accounting. so, yea.)

<@U053HNE90>: would you see any issue with moving the workdir lock under the workdir? other than the obvious `./pants clean-all` case, which wipes out the workdir. cc <@U0AR49RCK>

for scoot, we've been experimenting with alternate locations for the workdir

Well, clean-all is wiping out the workdir, and the lock is on the workdir, soo

As long as clean-all respects the lock, I suppose

<@U0AR49RCK>: i think one way to get access to that option at <https://github.com/pantsbuild/pants/blob/master/src/python/pants/pantsd/process_manager.py#L62> would be to have `ProcessMetadataManager` extend `Subsystem`, and then access its own options instance

<@U051221NF>: is there a better way than that ^ to get access to global options?

<@U053HNE90>: yea. as long as `clean-all` reacquires necessary locks i suppose?

I think it's to have the workdir lock move not to be *under* the workdir, but *next* to the workdir, and just sidesteps all of this.

My goal: pants should work with a read-only buildroot.

<@U0AR49RCK>: it's already next to the workdir probably?

We've seen that lock and also ProcessManager.

It's next to the workdir by default, but not if you set the workdir.

right... so either making both of them configurable, or having both of them live next to the workdir by default would probably be fine. but it's a bit strange to create something _outside_ of the configured directory

could also have some new config option that is "above" the workdir and all other locks

and then have pants_workdir default to `${mutable_root}/.pants.d`

mm, maybe. would be odd if `dist` went in there.