3 ms·
Does build-plan help with the case of including an artifact from another build system (e.g. data file for code-generation like SVD or libs to link against)? Wh
by epage 8y ago
Does build-plan help with the case of including an artifact from another build system (e.g. data file for code-generation like SVD or libs to link against)? What about someone not using build-plan but publishing crates, whether external or internal?
Speaking of, alternative crate indexes are something I think we need to do at some point for improved corporate support. It'll be interesting to explore the requirements. Some I can think of include
- Publish internal-only crates
- Some companies might want purely internal mirroring (for secured systems)
- Some companies might want a read-through cache to self-host what they use (for life-cycle management)
- Some companies might want to exclude crates (for extra-cautious licensing validation) which could make it hard to use anything unless we can also transitively exclude things
- steveklabnik 8y agobuild-plan is meant to be able to expose to an external build system the stuff that Cargo would want to build; it's not meant to talk about artifacts from other build systems. It's meant to help Rust fit in there, not to control other parts of the build. > Speaking of, alternative crate indexes are something I think we need to do at some point for improved corporate support. Absolutely! We accepted an RFC here, and there's an unstable implementation https://github.com/rust-lang/rfcs/blob/master/text/2141-alternative-registries.md https://github.com/rust-lang/rfcs/blob/master/text/2141-alte...