3 ms·
> We've been working with distros on packaging stuff; it's mostly sorted. Each distro is doing the thing that works for them. Have you worked with openSUSE, si
by cyphar 10y ago
> We've been working with distros on packaging stuff; it's mostly sorted. Each distro is doing the thing that works for them.
Have you worked with openSUSE, since as far as I know devel:languages:rust is still in the state of "we aren't sure how to deal with these problems". In particular, there aren't any rust rpm macros in openSUSE yet, so there doesn't appear to be a clear way to create an rpm for a particular Rust project.
I've written several things in Rust that I would love to package for our distribution, but I just don't know how we are meant to do it without depending on a network connection to download dependencies out-of-band (outside of rpms dependency system).
> Additionally, making sure we play well with other build systems is a big goal this year generally.
Yeah, that's the big problem at the moment. OBS provides huge benefits (rebuilds when dependencies change, tracking of security bugs and fixes) but it also has reasonable restrictions like not being able to connect to the internet.
Having a better story in this respect _really would_ help Rust in its adoption in distributions.
- steveklabnik 10y agoOpenSuse is a bit behind, say, Debian, but I thought there were people actively working on it. Las I remember, Rust and Cargo were packaged, but they weren't sure if they wanted to follow in Debian's footsteps and automatically convert packages or do something more manual like Arch. As long as ou have the stuff previously downloaded somewhere, offline builds of everything are totally supported; they're required not only by distros but by Firefox, for example.