Cabal
nixpkgs
Our great sponsors
Cabal | nixpkgs | |
---|---|---|
84 | 962 | |
1,559 | 15,311 | |
1.0% | 6.3% | |
9.8 | 10.0 | |
7 days ago | 1 day ago | |
Haskell | Nix | |
BSD 3-clause "New" or "Revised" License | 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.
Cabal
-
Would anyone be interested in hoot: A cabal wrapper for haskell based on Cargo?
Also, there's already a cabal RFC to support toml: https://github.com/haskell/cabal/issues/7548
-
On the verge of giving up learning Haskell because of the terrible tooling.
Cabal has a lot of dark corners once you stray from the happy path. Just checked and I'm currently subscribed to 37 threads on the issue tracker, and I'm not a maintainer. A lot of these are related to lesser-used features like cabal scripts, environment files and doctests (though I think all of these things would used more if they were more reliable), but there's also plenty of stupid stuff like: - https://github.com/haskell/cabal/issues/3313 - https://github.com/haskell/cabal/issues/8527 - https://github.com/haskell/cabal/issues/8391 - https://github.com/haskell/cabal/issues/7789 - https://github.com/haskell/cabal/issues/6888 - https://github.com/haskell/cabal/issues/6999 - https://github.com/haskell/cabal/issues/5271
-
There is No “Tooling Issue” in Haskell
By the way, there are some open issues for the command to add a package in Cabal.
-
Why GHCi is my new calculator
That's interesting. Could you could open a an issue about this? https://github.com/haskell/cabal/issues
- Any open source projects to contribute to for beginners
-
dr-cabal v0.2.0.0: Interactive output + critical path computation
At the moment, cabal-install doesn't support hpack natively but if the project can be build with cabal-install, you can run hpack manually to produce the .cabal file and utilise dr-cabal after that :)
-
Failure with cabal v2-test
Hm thanks for that, could try out some of those ideas. Here's the github issue i opened for this: https://github.com/haskell/cabal/issues/8580
-
Haskell adoption is higher than I expected, what can we do to get it to top 10 languages.
Would really love it if the Cabal documentation had this as its own, highly visible entry. I submitted a pull request to that end.
-
Monthly Hask Anything (September 2022)
Sometimes cabal's output is confusing with regards to optimization levels: https://github.com/haskell/cabal/issues/6221
-
Just released: cabal 3.8.1.0
Direct link to changelog: https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.8.1.0.md
nixpkgs
-
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?
That's doesn't happen in a single thread, but e.g. asynchronous multithreaded code can spit values in arbitrary order, and depending on what you do you can end up with a different result (floating point is just an example). Generally, you can't guarantee reproducibility because there's too much hardware state that can't be isolated even in a VM. Sure, 99% software doesn't depend on it or do cursed stuff like microarchitecture probing during building, and you won't care until you try to package some automated tests for a game physics engine or something like that. What can happen, inevitably happens.
We don't need to be looking for such contrived examples actually, nixpkgs track the packages that aren't reproducible for much more trivial reasons:
https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
- trim boto3/botocore, to remove all stuff I did not use, that sucker on it's own is over 100MB
The thing is what you need to understand is that the packages are primarily targeting the NixOS operating system, where in normal situation you have plenty of disk space, and you rather want all features to be available (because why not?). So you end up with bunch of dependencies, that you don't need. Alpine image for example was designed to be for docker, so the goal with all packages is to disable extra bells and whistles.
This is why your result is bigger.
To build a small image you will need to use override and disable all that unnecessary shit. Look at zulu for example:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...
you add alsa, fontconfig (probably comes with entire X11), freetype, xorg (oh, nvm fontconfig, it's added explicitly), cups, gtk, cairo and ffmpeg)
Notice how your friend carefully extracts and places only needed files in the container, while you just bundle the entire zulu package with all of its dependencies in your project.
-
Use Ansible to create and start LXD virtual machines
#!/usr/bin/env nix-shell #! nix-shell -i bash #! nix-shell -p sops #! nix-shell -I https://github.com/NixOS/nixpkgs/archive/refs/tags/23.05.tar.gz source config.sh "$@"
-
What AI assistants are already bundled for Linux?
NixOS just got tabbyml[1] which is built on llama-cpp. Working on systemsd services the weekend and updating latest tabbyml release which supports rocm in addition to cuda
-
Contributing Scrutiny to Nixpkgs
It's easy to open a PR, but not so easy to get someone to actually review it.
There's currently 165 open PRs by first-time contributors adding a new package, some of which have been just sitting there without review comments for years. https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+label%3A%22...
At least they're meticulously labeled so it's easy to find them.
- I Just Wanted Emacs to Look Nice – Using 24-Bit Color in Terminals
-
Going declarative on macOS with Nix and Nix-Darwin
I'm also using NixOS and working on Go projects, and had to deal with out-of-date Go releases. Nixpkgs generally does get the latest Go versions pretty quickly, but only in the unstable channels, they're not backported to NixOS releases. You can just grab that one package out of nixpkgs-unstable or nixos-unstable, like:
(import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/nixpkgs-unstable.tar.gz") {}).go_1_21
-
NixOS: Declarative Builds and Deployments
> What exactly would this "cleaner base" look like?
My interpretation would be something like: the abandonment of software that is so poorly designed that it is difficult to package and/or run under Nix.
This commit message (from one of my commits) details some of the struggles supporting Ruby under Nix:
https://github.com/NixOS/nixpkgs/commit/b6c06e216bb3bface40e...
Each of those problems is due to either:
1. Some unmotivated contrivance in Bundler, where the maintainers refused to make their stuff less needlessly broken, or
2. Ruby programmers in general not programming with packaging in mind (haven't touched Ruby/Rails professionally in a while, but when I did, it was par for the course to rsync/capistrano files around -- no one saw the utility of any sort of packaging)
And the two really reinforce each other. Bundler is the de facto way to declare and pin dependencies at the app level, but then Bundler makes it nearly impossible (see the commit message for details) to package software using Bundler, which reinforces the "fuck it, we'll just rsync files around over SSH", which means no one pressures Bundler to Do The Right Thing.
It's the same thing everywhere else. There are complaints elsewhere in this comment section about the nodejs/npm experience on Nix: same underlying problem. The design behind npm is so unnecessarily shit-tacular that it kinda sorta just barely works on its tier 1 platforms. I don't envy the brave souls that have worked on supporting npm packages on Nix.
What are some alternatives?
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
stack - The Haskell Tool Stack
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
git-lfs - Git extension for versioning large files
haskell.nix - Alternative Haskell Infrastructure for Nixpkgs
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.
nixos - My NixOS Configurations
youtube-dl-gui - A cross-platform GUI for youtube-dl made in Electron and node.js
devshell - Per project developer environments
Emu68 - M68K emulation for AArch64/AArch32