haskell-nix
nixpkgs
Our great sponsors
haskell-nix | nixpkgs | |
---|---|---|
6 | 972 | |
1,127 | 15,581 | |
- | 4.9% | |
2.7 | 10.0 | |
7 months ago | 6 days ago | |
Nix | Nix | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
haskell-nix
- Nix Team Creation
-
How should dependencies be specified for the Haskell C FFI with callCabal2Nix?
Here's a tutorial on using native dependencies.
-
Question about cabal and nix integration
Nevermind. I found a really good tutorial: https://github.com/Gabriel439/haskell-nix
-
What's all the hype with Nix?
Gabriel Gonzalez's haskell-nix is a far more palatable introduction tutorial, then they can make the choice of whether or not to buy into IOHK's haskell.nix ecosystem if it suits their needs.
-
Nix is the ultimate DevOps toolkit
I found useful this series of articles introducing Nix by using it with Haskell: https://github.com/Gabriel439/haskell-nix
I hope it helps.
nixpkgs
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
-
GitHub Disabled the Xz Repo
True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)
It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.
That is the problem.
-
Combining Nix with Terraform for better DevOps
We’ve noticed that some users have been asking about how to use older versions of Terraform in their Nix setups [1, 2]. This is an example of the diverse needs of people and the importance of maintaining backward compatibility. We hope that nixpkgs-terraform will be a useful tool for these users.
-
Nix is a better Docker image builder than Docker's image builder
I think whateveracct was referring to is this link:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...
What that file is doing, is building a package, and it essentially is a combination of what Makefile and what RPM spec file does.
I don't know if you're familiar with those tools, but if you aren't it takes some time to know them enough to understand what is happening. So why would be different here?
What are some alternatives?
haskell.nix - Alternative Haskell Infrastructure for Nixpkgs
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
nix-ros-overlay - ROS overlay for the Nix package manager
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
robotnix - Build Android (AOSP) using Nix [maintainer=@danielfullmer,@Atemu]
git-lfs - Git extension for versioning large files
nix-templates - Nix Flake templates for various languages
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
static-haskell-nix - easily build most Haskell programs into fully static Linux executables
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
Cabal - Official upstream development repository for Cabal and cabal-install
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.