NixOS

We now have a fairly complete set of KDE 4.2 packages in Nixpkgs and NixOS. Previously we had KDE 3.5, but it was rather incomplete: just kdelibs and kdebase. Now we have all that desktop goodness, such as ... [More] kdemultimedia, kdenetwork and kdegames. You can enable KDE 4 in NixOS by setting the services.xserver.sessionType option to kde4. Thanks go to Yury G. Kudryashov, Andrew Morsillo and Sander van der Burg for doing the hard work on adding KDE 4 to Nixpkgs. (Screenshot 1, screenshot 2.) [Less]

We now have a fairly complete set of KDE 4.2 packages in Nixpkgs and NixOS. Previously we had KDE 3.5, but it was rather incomplete: just kdelibs and kdebase. Now we have all that desktop goodness, such as ... [More] kdemultimedia, kdenetwork and kdegames. You can enable KDE 4 in NixOS by setting the services.xserver.sessionType option to kde4. Thanks go to Yury G. Kudryashov, Andrew Morsillo and Sander van der Burg for doing the hard work on adding KDE 4 to Nixpkgs. (Screenshot 1, screenshot 2) [Less]

Nix and NixOS releases are now built in Hydra, the new Nix-based continuous build system. Hydra replaces our old Nix-based build farm, which will be phased out soon. There are several advantages over the old ... [More] build farm: the build tasks for a project are scheduled and published separately, so that for instance a (fast) tarball build doesn’t have to wait for a (slow) Cygwin build; build results are stored in a database, which will enable all sorts of interesting queries; better error reporting; a better web interface; and much more. We have written a draft paper about Hydra. There are some instructions available about how to set up your own Hydra server. [Less]

Nix and NixOS releases are now built in Hydra, the new Nix-based continuous build system. Hydra replaces our old Nix-based build farm, which will be phased out soon. There are several advantages ... [More] over the old build farm: the build tasks for a project are scheduled and published separately, so that for instance a (fast) tarball build doesn’t have to wait for a (slow) Cygwin build; build results are stored in a database, which will enable all sorts of interesting queries; better error reporting; a better web interface; and much more. We have written a draft paper about Hydra. There are some instructions available about how to set up your own Hydra server. [Less]

Nix and NixOS releases are now built in Hydra, the new Nix-based continuous build system. Hydra replaces our old Nix-based build farm, which will be phased out soon. There are several advantages over the old ... [More] build farm: the build tasks for a project are scheduled and published separately, so that for instance a (fast) tarball build doesn’t have to wait for a (slow) Cygwin build; build results are stored in a database, which will enable all sorts of interesting queries; better error reporting; a better web interface; and much more. We have written a draft paper about Hydra. There are some instructions available about how to set up your own Hydra server. [Less]

Nix and NixOS releases are now built in Hydra, the new Nix-based continuous build system. Hydra replaces our old Nix-based build farm, which will be phased out soon. There are several advantages over the old ... [More] build farm: the build tasks for a project are scheduled and published separately, so that for instance a (fast) tarball build doesn’t have to wait for a (slow) Cygwin build; build results are stored in a database, which will enable all sorts of interesting queries; better error reporting; a better web interface; and much more. We have written a draft paper about Hydra. There are some instructions available about how to set up your own Hydra server. [Less]

Nix and NixOS releases are now built in Hydra, the new Nix-based continuous build system. Hydra replaces our old Nix-based build farm, which will be phased out soon. There are several advantages over the old ... [More] build farm: the build tasks for a project are scheduled and published separately, so that for instance a (fast) tarball build doesn’t have to wait for a (slow) Cygwin build; build results are stored in a database, which will enable all sorts of interesting queries; better error reporting; a better web interface; and much more. We have written a draft paper about Hydra. There are some instructions available about how to set up your own Hydra server. [Less]

Nix and NixOS releases are now built in Hydra, the new Nix-based continuous build system. Hydra replaces our old Nix-based build farm, which will be phased out soon. There are several advantages ... [More] over the old build farm: the build tasks for a project are scheduled and published separately, so that for instance a (fast) tarball build doesn’t have to wait for a (slow) Cygwin build; build results are stored in a database, which will enable all sorts of interesting queries; better error reporting; a better web interface; and much more. We have written a draft paper about Hydra. There are some instructions available about how to set up your own Hydra server. [Less]

There is an article on Linux.com about Nix: “Nix fixes dependency hell on all Linux distributions”.

There is an article on Linux.com about Nix: “Nix fixes dependency hell on all Linux distributions”.