nixpkgs
Home Manager using Nix
Our great sponsors
nixpkgs | Home Manager using Nix | |
---|---|---|
972 | 182 | |
15,581 | 5,863 | |
4.9% | 6.3% | |
10.0 | 9.8 | |
7 days ago | 3 days ago | |
Nix | Nix | |
MIT 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.
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?
Home Manager using Nix
-
Cosmic Desktop: Hammering Out New Cosmic Features
It's probably overkill for what you are trying to do. But I have been using home-manager [0] as a way to quickly restore my working environment.
[0] https://nix-community.github.io/home-manager/
-
How do I actually update home-manager?
$ home-manager --version 23.05 $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-23.11.tar.gz home-manager $ nix-channel --update $ nix-shell '' -A install [...] All done! The home-manager tool should now be installed and you can edit /home/MY-USERNAME/.config/home-manager/home.nix to configure Home Manager. Run 'man home-configuration.nix' to see all available options. $ home-manager --version 23.05
-
Possible to use KDE plugins on nixos?
Unfortunately until we find more volunteers in this area, it is hard to see status quo changing. See also https://github.com/nix-community/home-manager/issues/607 and this ongoing project https://github.com/pjones/plasma-manager
- Exclude packages in home manager
-
An Overview of Nix in Practice
> Channels are, AFAIU, a reference to some point-in-time/commit/version of nixpkgs
It's not specifically nixpkgs, but any Nix code generally.
Per the Nix manual[0]:
> Channels are a mechanism for referencing remote Nix expressions and conveniently retrieving their latest version.
e.g. home-manager's suggested channel is just the github tarball for the relevant branch[1]:
nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
-
Fake recruiter Lazarus lured aerospace employee with trojanized coding challenge
It sounds like you'd benefit a lot from Nix/NixOS [1], if not just home-manager[2].
1. https://nixos.org/
2. https://github.com/nix-community/home-manager
-
Noob question: Where home-manager config after installed on archlinux
nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager nix-channel --update nix-shell '' -A install
-
Need help on home manager neovim config
I'm using flakes and home manager and not really sure how to go about managing my neovim configuration. I've read through some other posts, github issues, and various articles trying to suss out a good way to do this. Reading through other people's configs and posts was somewhat helpful but there is a lot going on I don't understand and everyone's examples I've seen vary wildly.
-
Recurring 'Home Manager not found' Error After Running nix-collect-garbage"
Said store path contains the home-manager repo. After the home-manager run, the store path is recreated.
-
I want to like NixOS but... I can't and I need some help
I can't answer all your questions, but home-manager does have a dconf module that would probably be better to use than that external tool. Everything inside the options block are the things you can pass to the dconf module.
What are some alternatives?
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
git-lfs - Git extension for versioning large files
GNU Stow - GNU Stow - mirror of savannah git repository occasionally with more bleeding-edge branches
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
nixos-flake-example - This is a demo NixOS config, with optional flakes support. Along with notes on why flakes is useful and worth adopting.
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
NixOS-WSL - NixOS on WSL(2) [maintainer=@nzbr]
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]
nixos - My NixOS Configurations
chezmoi - Manage your dotfiles across multiple diverse machines, securely.