4 ms·

Maybe the problem is the rust community seems to live on the bleeding edge and always needs to have a ‘nightly’ build to do anything interesting? And distros u

Maybe the problem is the rust community seems to live on the bleeding edge and always needs to have a ‘nightly’ build to do anything interesting? And distros usually don’t bump versions between releases because they just don’t. Run Debian Sid or Fedora Rawhide or <whatever> if that’s what you’re after.

dheera 4y ago
It's straightforward to set up an apt-get repository that updates nightly and have users use that. For something as widespread as Rust I expect better than curl | sh scripts.
- FridgeSeal 4y ago
  Well I guess that solves the issue for one OS/distro. It’s probably not _why_ they did it, but I certainly like that regardless of OS, installation is the same and it’s reliable.
  - steveklabnik 4y ago
    It is a major part of why we did it. Giving everyone a nice flow for getting up and going matters for adoption.
    - FridgeSeal 4y ago
      That’s awesome. For what it’s worth, I had a C# dev who’d never dealt with Rust at all before get themselves setup, and then compiling and running the Rust app by themselves in about 10 minutes flat (our internet is slow) and I definitely think the ease of the setup flow contributed to that hugely, so massive thanks for making it so nice.
- UncleEntity 4y ago
  Probably doesn’t matter for Rust but once you start messing with random system packages that other packages depend on it becomes less than straightforward really quick. One simple version bump can effect hundreds of packages and, if you’re not careful, bork an entire install… ask me how I know that one. —edit— Also should say that I’m fully in the package manager camp. If I want to install something that’s not in the repos I almost always find or make a package and build it locally because I don’t want random orphaned files strewn around my system folders. Unless it’s just some command line program then I usually just use it from the source directory and don’t even bother having it in my path.
- steveklabnik 4y ago
  Many Rust users are on platforms that apt does not support.
nindalf 4y ago
> rust community seems to live on the bleeding edge and always needs to have a ‘nightly’ build to do anything interesting You have an example of a project that needs nightly to build? I’m sure some exist, but nearly all libraries and projects live on the latest stable release.
- doodlesdev 4y ago
  That indeed used to be very common in the early days of Rust, however, I believe stable Rust is what most libraries and projects use nowadays. It's been some time since I saw anything that used Rust beyond 1.60 (release April last year) as a minimum version.

dheera 4y ago

It's straightforward to set up an apt-get repository that updates nightly and have users use that. For something as widespread as Rust I expect better than curl | sh scripts.

FridgeSeal 4y ago
Well I guess that solves the issue for one OS/distro. It’s probably not _why_ they did it, but I certainly like that regardless of OS, installation is the same and it’s reliable.
- steveklabnik 4y ago
  It is a major part of why we did it. Giving everyone a nice flow for getting up and going matters for adoption.
  - FridgeSeal 4y ago
    That’s awesome. For what it’s worth, I had a C# dev who’d never dealt with Rust at all before get themselves setup, and then compiling and running the Rust app by themselves in about 10 minutes flat (our internet is slow) and I definitely think the ease of the setup flow contributed to that hugely, so massive thanks for making it so nice.
UncleEntity 4y ago
Probably doesn’t matter for Rust but once you start messing with random system packages that other packages depend on it becomes less than straightforward really quick. One simple version bump can effect hundreds of packages and, if you’re not careful, bork an entire install… ask me how I know that one. —edit— Also should say that I’m fully in the package manager camp. If I want to install something that’s not in the repos I almost always find or make a package and build it locally because I don’t want random orphaned files strewn around my system folders. Unless it’s just some command line program then I usually just use it from the source directory and don’t even bother having it in my path.
steveklabnik 4y ago
Many Rust users are on platforms that apt does not support.

nindalf 4y ago

> rust community seems to live on the bleeding edge and always needs to have a ‘nightly’ build to do anything interesting You have an example of a project that needs nightly to build? I’m sure some exist, but nearly all libraries and projects live on the latest stable release.

doodlesdev 4y ago
That indeed used to be very common in the early days of Rust, however, I believe stable Rust is what most libraries and projects use nowadays. It's been some time since I saw anything that used Rust beyond 1.60 (release April last year) as a minimum version.