Carter Anderson

Maybe we can compress it by removing redundant license boilerplate? no clue if that is valid.

I dig that. We could have a bevy_license_compliance plugin that `include_bytes!()` the gzipped license, adds support for a command line: ```--print-bevy-licenses``` argument, and provides a function to get the full...

And then (depending on the size) we could include it by default.

My personal vote is for "leave it as is". There is no harm in cataloging this information and making it available to people that encounter the issue and/or are interested...

To be clear, my position is "lets not close out these issues, and we should encourage people to both file them and investigate them". I'm on board for attempting to...

> Part 1: Conditional System Compilation This feels laborious, boilerplatey, and error prone (as it is not driving behaviors but rather _attesting_ that these behaviors are present). These features would...

> but hiding this behind something that appears as a "common resolution" is not the way it should be done I agree. Any "opinionated" view of available resolutions is a...

The implemented behavior is what we want. The documented behavior was intended to capture the implemented behavior: > recursively visit the require list of each of the components in the...

I think re-exporting cosmic text in its entirety should be reconsidered. Imo it should largely be an implementation detail, except for advanced use cases. People in that position can just...

All of the examples in the original message work for me (I just checked them off in the message). I've tested all of the other examples mentioned and they either...