Wren Turkal

Well, one nice thing is the other frameworks seem to be creating compatible env vars inside their containers. It would be nice to get maestro on that train also.

I think it might be better if we say that the generator_url must point to an archive that has a cargo-bazel file at the root that is executable. I am...

I think it might be better if we say that the generator_url must point to an archive that has a cargo-bazel file at the root that is executable. I am...

I think this might be better if made the generator_urls point to archives that have an executable file at a known location inside them. I don't know if download_and_extract will...

Okay, so I have changed to using the tar directly with download_and_extract. This is better. However, there is still a problem in that it only support `.tar.xz` files because I...

That seems needlessly complex. What are the build files, and why do I have to manually create them? What do they even look like? Also, that looks like it would...

Okay on the build file thing. Thanks for explaining. > The reason I lean away from adding the functionality to the rule itself is because I think it adds hidden...

The `.xz` type is fundamentally different from those that are supported. It is not an archive format. It's only compression. The `download_and_extract` function is meant to download and extract and...

Okay, so what is the way forward that would be acceptable? My recommendation is the adding the generator_url_type attr to the crates_repository, and using `"binary"` as the default with the...

I personally would like to see the example landed somewhere. Is it possible that there should be a repo somewhere that just holds multilanguage examples instead of landing this in...