#general
- e
enough-analyst-54434
09/09/2015, 2:19 AMand thiose that can have edges - e
enough-analyst-54434
09/09/2015, 2:19 AM@witty-crayon-22786: that can work for some cases, and maybe all - yes - e
enough-analyst-54434
09/09/2015, 2:20 AMnot sure about that - e
enough-analyst-54434
09/09/2015, 2:20 AMits a ui weirdness, how as a use do I know when to do which? - w
witty-crayon-22786
09/09/2015, 2:20 AMconfiguration (EDIT; pants.ini) does not go away entirely unless you can place all of your configuration in the graph - b
bored-art-40741
09/09/2015, 2:20 AM@enough-analyst-54434: I think in the end I came up with this: you scan the Payload for fields of a certain subtype, and proxy/hydrate them at traverse_dependency_specs time - e
enough-analyst-54434
09/09/2015, 2:20 AMk - b
bored-art-40741
09/09/2015, 2:21 AMThat's my vague clue from distant memory, not anything concrete and final - e
enough-analyst-54434
09/09/2015, 2:21 AMok - good to keep in mind though - b
bored-art-40741
09/09/2015, 2:21 AMI just remember being convinced that it was the way to stay most sane - b
bored-art-40741
09/09/2015, 2:21 AM@witty-crayon-22786: What you're saying is more or less what I decided after trying this. But enough time has passed and the interface has settled enough that I'd be happy to see someone else try - b
bored-art-40741
09/09/2015, 2:22 AMThere were compelling use cases - e
enough-analyst-54434
09/09/2015, 2:22 AMBasically @witty-crayon-22786 configuring things repo wide make sense in pants ini, but then using those configured things in Targets defined in build files - as opposed to Tasks is mushy - e
enough-analyst-54434
09/09/2015, 2:22 AMDo I say repo='public' - b
bored-art-40741
09/09/2015, 2:22 AMThe one master issue though is that all addressable instantiation in BUILD files is proxied, and you always have to dance around that proxy layer - e
enough-analyst-54434
09/09/2015, 2:22 AMAnd happen to know that 'public' is defined in some appropriate [section] in pants.ini? - e
enough-analyst-54434
09/09/2015, 2:23 AMa //:public is much cleared - I think - for a BUILD file author - e
enough-analyst-54434
09/09/2015, 2:23 AMits clear what that means - there's an algorithm to go find the definition of //:public - w
witty-crayon-22786
09/09/2015, 2:23 AMthen should all objects go in the graph? - w
witty-crayon-22786
09/09/2015, 2:23 AMwhy this object? - e
enough-analyst-54434
09/09/2015, 2:23 AMpotentially yes - e
enough-analyst-54434
09/09/2015, 2:23 AMThat Targets consume - w
witty-crayon-22786
09/09/2015, 2:24 AMi'll buy that, but it's not foolproof - w
witty-crayon-22786
09/09/2015, 2:24 AMthere are lots of default parameters in subsystems - w
witty-crayon-22786
09/09/2015, 2:24 AMtargets "consume" configuration - e
enough-analyst-54434
09/09/2015, 2:24 AMMost Subsystems are used only by Tasks - e
enough-analyst-54434
09/09/2015, 2:24 AMScalaPlatform and ... 1 other by Targets - w
witty-crayon-22786
09/09/2015, 2:24 AMwe have two more internally - e
enough-analyst-54434
09/09/2015, 2:24 AMsketch what they do - w
witty-crayon-22786
09/09/2015, 2:25 AMwell, one is approximately scalaplatform, heh. should upstream that.