Le 23/01/2018 à 13:15, John Paul Adrian Glaubitz a écrit :
On 01/23/2018 11:42 AM, Hadrien Grasland wrote:
Then maybe your time would be better spent working together with the Rust team to ensure that they can and do run their tests on armhf as well?
Am I the person who is trying to push Rust everywhere?
Rust upstream wants Rust to succeed as a systems programming language. It's therefore their responsibility to make sure the compiler works properly on the supported targets.
If they cannot achieve that, they should stop trying to claim how superior Rust is over other languages and stop trying to push it as a systems programming language.
I am already doing lots of upstream work in various projects. But this isn't my main job, so you can't expect me to do the homework of the Rust developers.
Adrian
I appreciate your point of view. Indeed, improving upstream testing should not be your main job as a distribution maintainer. That being said, there is a reason why Debian lends testing hardware to projects like the FreePascal compiler: while it is probably not the right thing to do, it is both the nice and the pragmatic thing to do. Given Rust's immense productivity benefits in the system programming space with respect to C and C++, people are bound to use it. Much like they use bleeding-edge C++, Node.js, custom package managers like Maven and PyPI and all other kind of programming environments which make the life of distribution maintainers hard. It is unescapable, in the sense that you cannot simply wish the language and its implementation away from your radar, rant about every Rust-based package that you see pass by, and be done with it. What happens to librsvg today, is happening to gstreamer and other GNOME projects tomorrow, and at some point you will need to face the issue anyhow. Given that, the next best thing to do after obliterating the perceived nuisance is to work on making the product better so that it fits your needs. This is what distribution maintainers have always done: if the project is not quick enough, write the patch yourself, and send it to upstream with a friendly note. Backport fixes from newer versions into the version that you distribute. Help the developer test on new architectures that the distribution supports. Ultimately, these kind of actions benefit the distribution too. Which is why I am saying that working with the Rust community might be more productive, and ultimately beneficial to you, than merely complaining about its current state. Hadrien -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org