Generally speaking this is a two-part problem. Firstly, the build system needs to support something along the lines of a needs_build flag which a resource can raise. In order to support that functionality the build system needs some way to allow a resource to store a value and test against that vale in the next call.
In one model this process is tightly controlled by the builder, and in another it is delegated to the individual resources. Making that decision will probably come down to a trade-off between performance and flexibility.
Remember, blanket is not bazel, so we don't necessarily have to go nuts here. This should be considered in parallel with #14.
Generally speaking this is a two-part problem. Firstly, the build system needs to support something along the lines of a
needs_buildflag which a resource can raise. In order to support that functionality the build system needs some way to allow a resource to store a value and test against that vale in the next call.In one model this process is tightly controlled by the builder, and in another it is delegated to the individual resources. Making that decision will probably come down to a trade-off between performance and flexibility.
Remember, blanket is not bazel, so we don't necessarily have to go nuts here. This should be considered in parallel with #14.