Well, there is no point to take the survey as to quote from the reported bug:

I think that would probably be easy enough to comply with. I also
think that is fairly in line with trademark policies in general. If
someone significantly modifies Debian, I believe the Debian Project
would insist that they use a different name for their product despite
the DFSG and despite that Debian is free and open source.

So the people are complying further with trademark, copyright (instead of copyleft) and branding. No need to go with it - for me speaking now. Point is: There is no understanding of that issue until today. But there is more: https://bugs.debian.org/cgi-bin/bugrepo … ug=1015242

So I say: Let them clear this up. Either there will be gcc-rust coming or not. Until that point I think we as community should not bother further with it. When there is gcc-version with correct including rust without law-issues: We can look again onto that point and perhaps than having more. I hope they solve it the same way gcc-go has done: No sideloading packages like GO is doing official. No thanks at all! We have ONE package-management. There is no need for another one within other packages.

And yes: We can help us, but therefore giving a hand would be nice. When there is some feedback about the flaws of Rust already noted: Okay, we will help for sure. But running after those discussions will leave our concrete focus for the moment.

There is no need to do that: It is not only Rust. And per definition they "defend their trademark" further. So when we remove Cargo we need to ask again for permission. That's not okay. Furthermore: You need servo, for building servo you need rustup and for building a newer version of Mozilla Firefox you also need the libc-implementation for WebAssembly. That's bloat per definition: When I need so much tools for just compiling a program, that's not acceptable in any way.

Just to note about the links:

https://github.com/rust-lang/rustup.rs
https://servo.org/
https://github.com/WebAssembly/wasi-libc

So this reply is also in relation of the team: We are focussed onto bugfixing, adding minor helpers and most the time HyperbolaBSD and porting! We have no time to attend into some surveys with unclear outcome, especially when projects ask for feedback never willing and showed up the will to recognize the problem. We will put focus on our system, making it the best possible for us. Rest is up to the community! But to note: You cannot just add Rust and be then fine with compiling newer versions of firefox for example. The links and names for dependencies show up a different picture. You don't want more bloat included? Okay, stay away from the Rust-toolchain and therefore Rust in a whole.

Just because there is a 64bit-system with more resources for accessing does not mean we are there to misuse those and build even bigger programs and complex toolchains. In the end somebody has to understand all that and we as small team have neither the resources nor the time to do that. Support is needed nevertheless: Donating includes not also money. If Rust is going so missing, then please do something on your own. Our focus lies not onto that part for sure!