Results from the openSUSE 2021 Rust Survey (opens in new tab)

(fy.blackhats.net.au)

4 pointsaplanas4y ago3 comments

3 comments

I submitted this entry because IMHO is the first survey, that I am aware of, that is giving some data about the Rust toolchain inside a distribution.

I guess that openSUSE can be a bit different than Debian or Fedora, but there are some answers that for me are not expected. For example, the "In your ideal workflow, how would you prefer to manage your Rust dependencies?" question seems to favor cargo, instead a distribution package. That raises to me a lot of questions about how in this workflow we can have long time supported packages, when we need to backport fixes into dependencies that are not supported anymore upstream.

Wulf_4y ago

Could you give an example package you'd prefer to manage with your distro's package manager instead of cargo?

aplanasOP4y ago

Anyone that needs to be maintained for a long period of time. For example: Firefox.

Today Firefox have all the rust deps bundled (similar to cargo bundle). If / when tomorrow the maintainer of the distribution find a bug in one of the rust dependencies, s/he needs to add the fix inside the bundle without a clear process (1. do I need to fork and update Cargo.toml to point to my branch? 2. can I add the fix as a .patch and apply it after it gets unbundled by the build server? 3. ...)

An also this process needs to be repeated for each application that have this version of the crate as a dependency, and again without a clear way of identifying those applications that are affected.

j / k navigate · click thread line to collapse

3 comments

aplanasOP4y ago

I submitted this entry because IMHO is the first survey, that I am aware of, that is giving some data about the Rust toolchain inside a distribution.

Wulf_4y ago

Could you give an example package you'd prefer to manage with your distro's package manager instead of cargo?

aplanasOP4y ago

Anyone that needs to be maintained for a long period of time. For example: Firefox.

An also this process needs to be repeated for each application that have this version of the crate as a dependency, and again without a clear way of identifying those applications that are affected.

j / k navigate · click thread line to collapse