On 20 Nov 2019, at 18:35, Dany Marcoux <dmarcoux@suse.de> wrote:
On 19-11-20 00 h 55, William Brown wrote:
On 20 Nov 2019, at 03:04, Dany Marcoux <dmarcoux@suse.de> wrote:
On 19-11-19 16 h 44, Ludwig Nussel wrote:
William Brown schrieb:
[...] Due to the fast release cycle, developers aggressively using new features, and the npm style micro dependency system we have a recipe for problems - if you are not using the latest stable compiler, it's extremely likely that your libraries, or their dependents may not build on your project. Which is exactly the issue I have run into where rust on fedora 30 and opensuse leap 15.1 are simply too old to support the features that have been used in the last 6 months by library developers. From what I can tell Rust has two use cases in the stable distros. The first one is that it's needed by other system components. Regularly updated, more or less leaf packages Firefox as but unfortunately also as low as librsvg. For packages like the latter we most likely do not want Rust to change very six weeks, especially when that kind of use case spreads. So for that it would be better to upgrade the system Rust only for service packs ie once per year.
The other use case is developers that want the latest and greatest for their own purposes. For that it should be possible to create a parallel installable Rust package and regularly provide newer versions for it. That works for Leap via regular maintenance updates as well as SLE via Package Hub. I've been told that Rust is meant to be pretty good at backwards compatibility so it's probably sufficient to provide one additional Rust package that follows upstream releases, instead of a new one for all kinds of versions like eg Go does.
cu Ludwig
rustup[0] is what developers should use when developing in Rust. It's the
official Rust toolchain installer. I packaged it in my home[1] and submitted
a request[2] in hopes that it would get into Factory, but in the end, I didn't
get much feedback beside from Neal Gompa. I decided to revoke the request. As
you can see in the request, I talked about rust and rustup coexisting, but this
would need a bit more work. I didn't look into this, but I'm willing to do it.
It definitely seems to be possible as documented[3] upstream. This does not address the issue - how do we get from development to a system-buildable and shippable project. This is key here, we need to think about that full experience from development to deployment - not just development.
Right now, we have nothing for the development part, unless we want to stick to
whatever rust version openSUSE provides (which is a bad developer experience).
This is what my proposal would address.
We can not seperate deverloper from the deployment - else we fragment the experience and end up back here. No, the solution for how we ship and develop must be the same.
[0]: https://github.com/rust-lang/rustup
[1]: https://build.opensuse.org/package/show/home:dmarcoux/rustup.rs
[2]: https://build.opensuse.org/request/show/684463
[3]: https://github.com/rust-lang/rustup#working-with-distribution-rust-packages
-- Dany Marcoux <dmarcoux@suse.de> Full Stack Web Developer - Open Build Service
SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs
-- Dany Marcoux <dmarcoux@suse.de> Full Stack Web Developer - Open Build Service
SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
— Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org