SJ
@tdyas Just to loop back on this. From the discussion, it doesn't seem like there is any pushback to the feature - just a bike shed on `Builtin` for something...
Does DaemonGoal here imply that the usage is a long-running "server-ish" mechanism? Like a BSP or LSP? Or can I still run a one-off command (e.g. `pants plugin init --foo...
This will involve some interesting re-thinking. Swift operates at the "module" level, so Package.swift is top-level, and then all sources are bundled together and compiled as a module (similar to...
Review this before any Swift support: https://github.com/apple/swift/blob/main/docs/Driver.md And maybe this to help with dep inference: https://github.com/apple/swift/blob/main/docs/DependencyAnalysis.md
For backends, it's much easier to just work in the mainline fork: https://github.com/sureshjoshi/pants/tree/cc-first-party-compilation
Using this repo right now for example code, and then `pants_from_sources` for the `cc` stuff.
See https://github.com/pantsbuild/pants/pull/16424
Alternatively, can we add platforms fields to the `pex_binary` ourselves? We have minimum python version + architectures already.
Docker does this to some extent, so it should be possible - but we'll probably need to parse yaml files
@lilatomic had a lot of good ideas about this. Essentially, as roles/collections have a dedicated [folder structure](https://docs.ansible.com/ansible/latest/dev_guide/developing_collections_structure.html#collection-structure) - determining the source root and then using that folder type to figure...