92
Some Works In Progress You're Looking Forward To? (sh.itjust.works)
submitted 2 years ago by to c/linux@lemmy.ml
64 comments fedilink hide all child comments
 

What are some exciting projects that you follow and hope to see progress on?

I'll start!

  • Wayland greeter on SDDM
  • rust support on gcc
  • more Wayland adoption (especially VSCodium & Firefox forks)
  • Reproducible Build
  • ReactOS
you are viewing a single comment's thread
view the rest of the comments
[–] 18 points 2 years ago (1 child)

More nixOS development. It's the reproducible builds on the OS scale, one configuration file that will always generate exactly the same system when run, and you can update and rebuild from that file without restarting the system in most cases. This should make triangulating and fixing distro issues much easier, as well as making a distro easier to maintain from the user side.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (2 children)

    Wait, it's like docker, but for entire OS with packages, configuration and stuff like that?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 6 points 2 years ago* (2 children)

    Yes, and every package specifically defines the exact version of its libraries that it needs and the system symlinks everything together package by package, so there's no chance than an update will break something further upstream. The configuration file also controls things like MySQL configuration and user permissions so you can get literally the exact same system. I think even docker doesn't control for library versions with its regular configuration.

    EDIT: And it keeps older versions of the configuration file and its symlink arrangement around, so if something goes wrong, you can reboot the machine and select an older version from the bootloader.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago

    Definitely docker (well, let's say containers) control the library version, if you didn't build the image specifically not to do that (e.g. fetching dependencies at runtime, which is generally a bad practice and not the default).

    However, at build time if you use things like "apt install ..." You will get different versions depending on when you build the image, but once the image is built, you have always the same software inside. Obviously it is very different from nix as they serve very different purposes (one day I will find the motivation to switch to nixOS!).

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago

    Better than Docker in terms of reproducibility. While Docker containers are usually more or less reproducible, Docker images are not as the Dockerfiles depend on lots of external state such as the repositories of the distro used as a base image. This is also partially true for NixOS, but it's far more realistic to pin a version of nixpkgs (the Nix(OS) repository) than do the same with Debian repositories. The new Flake format even provides a way to pin nixpkgs by default.

  • permalink
  • fedilink
  • source
  • parent