nixpkgs-config
rfcs
nixpkgs-config | rfcs | |
---|---|---|
15 | 51 | |
139 | 488 | |
- | 2.5% | |
6.2 | 4.6 | |
4 months ago | 4 days ago | |
Nix | ||
- | Creative Commons Attribution Share Alike 4.0 |
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-config
-
Diving straight into flakes with no channels?
You can also take a look at my server configuration which uses flakes. And my separately-managed home-manager configuration which also uses flakes
-
So I’m hooked on this declarative configuration business. How deep does the rabbit hole go? Can I “rice” my desktop with just one file?
My "rice": https://github.com/jonringer/nixpkgs-config
-
libstdc++.so.6 => not found
I configure my neovim through home-manager. My configuration. Pulling vimPlugins from nixpkgs should give you something which works with NixOS (or anywhere for that matter, NixOS is essentially a clean room).
-
A Cross-Platform tool to deploy dot files
My dot file repo.
-
Using NixOS and Arch on separate machines
Home-manager link My example setup
-
Neovim unstable
Reference: - home.nix entry - Which refers to it's own dedicated file
- should i move all my pkgs from configuration.nix and move to home manager?
-
Installing every Arch package
If you want to take nix for a spin, i would recommend trying home-manager. It's essentially NixOS, but for dot files. It can install packages and services in addition to manage configuration. Also, I've been able to get it work on NixOS, WSL2, ubuntu, and macOS. Personal configuration if you're curious how it would look.
-
The Curse of NixOS
> And about Home Manager, the reason why I think it's over-hyped is because it provides a declarative approach to something that was... already declarative. Your $XDG_CONFIG directory does not need a leaky Nix abstraction on top of it
I don't really agree, I spent about 30mins to get my home-manager config to support an m1 mac [0]. I don't really want to think how long it would take me to look up all of the homebrew package names, and learn a new package manager. Instead, I just pushed all of the linux-specific items into their own bin, a little more logic, and I was able to get back to a comfortable terminal + git + vim settings.
Also, nix exposes congruent configuration management[1]. The state of my system is an exact reflection of the configuration. With other tools like ansible, vagrant, etc, I would get reconciliation configuration which is close on initial install but configuration drift is an ever-present concern; not to mention that large recipes and playbooks can take a very long time to run. Going the homebrew route would be divergent configuration, it would be very hard for me to get back to a certain configuration. With nix (and by extension home-manager), I can version control the configuration, improve it, roll it back, w/e I want.
> Why would I write my i3 config in Nix??
You do get some type checking, although the iteration time would probably be similar. You could also just do `xsession.windowManager.i3.extraConfig = builtins.readFile ./i3.config;` if you really just wanted to wholesale read in your existing profile.
> I'd rather just use `nix-env` personally.
nix-env is a double edge sword. You can rollback (somewhat, I believe it's just a stack of all changes), which is an improvement. However, nix only retains the "derivation name" to try and management. But for packages like python38, if you try to upgrade it, it will determine that `python-3.11-a3` is the package which is the most up-to-date. I try to discourage using nix-env.
[0]: https://github.com/jonringer/nixpkgs-config/commit/37ddfefa1...
-
Where are alacritty and systemd specified to install?
Here and full config here
rfcs
-
Nix: The Breaking Point
You may consider this view biased, but we have this: https://srid.ca/nixos-mod
* September 2023: The "Nix Community Survey 2023" is looking for gender data, and the mods don't like that most contributors are men.
* November 2023: The moderation team tries to institute a Code of Conduct https://github.com/NixOS/rfcs/pull/114 ... and they get their way
* November 2023: Some are not happy about it: https://discourse.nixos.org/t/moderation-team-accountability... -- the moderators talk about their "authority" and of course lock and hide the thread. It's "disruptive" and "off-topic", you see.
* This sort of activity continues -- moderators consolidating and increasing their power, citing how they need the power to control "concern trolls" and such -- and now in April 2024, we get https://save-nix-together.org/
The "anonymous contributors" want to drive out the NixOS founder entirely, so that _they_ are in charge. They want "to hold people accountable for bad behaviour at all levels" and lament having "responsibility without authority" - in other words, they want power, power, power. They want power over everyone. Their justification is that they believe they have the moral high ground, and they deserve to lord it over everyone else.
Hold onto that hard power, Eelco, and tell this lot to fork the project. Let's see how they enjoy moderating noxious.org instead of nixos.org
-
What Nix Will Have Been
https://old.reddit.com/r/NixOS/comments/1ceiz36/thoughts_on_...
And the RFC to improve the situation:
https://github.com/NixOS/rfcs/pull/175
-
Eelco Dolstra's leadership is corrosive to the Nix project
> (after eelco ignored the PR for quite a while, also!)
Clicking that link takes us to a PR that was opened on 2024-02-02. The initial response from the Nix author comes 7 minutes later. Puck has multiple back and forths with other members Github, but her next interaction with the Nix author comes the next day on 2024-02-03. This is also the first time in the conversation where she "reminds him ... to even read her PR message". There's a second interaction later that same day during which she does similar, but it's worth noting this is pointing to a different message and appears to be less a "reminder to read" and more re-iterating what they feel is their argument against the Nix author's own arguments. Puck then continues to have back and forth with other commenters but as of today, there has been no further comments from the Nix author after 2024-02-03, and no further comments from Puck after 2024-02-08.
This hardly to my mind qualifies either as "having to remind him multiple times to even read her PR message at all" or "after eelco ignored the PR for quite a while, also!" So as I said it's a fairly weak claim, and feels more like a "bastard eating crackers" reaction to the PR than an actual showing of poor behavior.
As for the "Meson example", I didn't ignore it. As I stated in my comment, I had at that point read two of the referenced discussions in detail, and thus commented on them. I didn't comment in the "Meson example" for the simple reason that I hadn't read it.
I have read it now, and equally find it confusing.
1) The claim in the letter is that the proposal has "passed RFC, for five years", yet the RFC itself only appears to have been opened 2022-08-24. It's been a while since grade school for me, and I'll admit COVID has warped all our sense of time, but I'm pretty sure 2022 is not 5 years ago.
2) The first completed working implementation of the change doesn't appear to have been done until 2023-01-18 (https://github.com/NixOS/rfcs/pull/132#issuecomment-13874661...). Again this is much less than 5 years old.
3) On 2023-03-20, the author of the PR for this change states:
> the RFC has made it past most of the early stages and the current goal is to achieve parity with the current buildsystem before replacing it.
(https://github.com/NixOS/rfcs/pull/132#issuecomment-14768433...)
Again, this doesn't seem to fit at all with the claim that the proposal has "passed RFC, for five years"
4) On 2023-11-01, the Nix author themselves asks for updates on the RFC implementation, an action which doesn't seem congruent with someone who is willy nilly single handedly blocking things and being a disruption to the process. And the author of the PR states:
>the main block is actually a lack of free time for the main devs!
(https://github.com/NixOS/rfcs/pull/132#issuecomment-17890770...)
This doesn't seem to point to evidence that the Nix author is single handedly holding up this process.
5) On 2024-03-21 the PR author notes:
> currently working on adding support to build nix-perl, waiting for assistance
(https://github.com/NixOS/rfcs/pull/132#issuecomment-20135356...)
Not to sound like a broken record, but if the issue isn't finished as of a few weeks ago, it can hardly be considered to be held up by the Nix author for 5 years.
I agree that one of the links in the open letter is to a comment on a PR from 2019, which is indeed 5 year ago, and does indeed contain the Nix author commenting that they are skeptical of the change because "he doesn't know meson but knows his own build system". But given that there's an entire wealth of history on the topic since then, including progress on the feature that appears completely unobstructed by the Nix author and an open PR that is a mere 3 weeks old for a current implementation, I find myself again unconvinced of this rampant bad behavior on the part of the Nix author. And I reiterate again that these complaints are very weak and don't do much to support the open letter at best, and act as contrary evidence at worst.
Again there might be other context to be had that is missing, but if one is going to write a massive "open letter" complaining about bad behavior, I expect the links in that letter to point to actual bad behavior, and or provide the relevant context necessary to show how what appears to be normal dissent is a passive aggressive continuation of obstruction. I have to assume the links one provides in an open letter is their strongest evidence, and if this is all the authors have... I am unconvinced.
-
Build System Schism: The Curse of Meta Build Systems
Nix with dynamic derivations (RFC92) could potentially beat this curse.
https://github.com/NixOS/rfcs/blob/master/rfcs/0092-plan-dyn...
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
See: A plan to stabilize the new CLI and Flakes incrementally https://github.com/NixOS/rfcs/pull/136
- RSS can be used to distribute all sorts of information
-
I like gentoo's package deprecation process
NixOS recently introduced "problem" infrastructure to deal with such problems more gracefully and explicitly:
https://github.com/NixOS/rfcs/blob/master/rfcs/0127-issues-w...
-
NixOS and Flakes Book: An unofficial book for beginners (free)
For some more context: Flawed as they are, Flakes solve a large number of problems Nix experiences without them. This is why I, and presumably many others, use them even in their current experimental state.
An RFC was recently accepted to commit to forming a plan towards stabilization of Flakes: https://github.com/NixOS/rfcs/pull/136
Personally, I don't believe there won't be any breaking changes, but I also believe that the stabilization of Flakes is still a ways away and hope that there will be a reasonable migration path.
- NixOS RFC 136 approved: A plan to stabilize the new CLI and Flakes incrementally
- NixOS RFC 136 accepted: A plan to stabilize the new CLI and Flakes incrementally
What are some alternatives?
base16-nix - Home manager module for themeing programs with base16 templates
nix-ros-overlay - ROS overlay for the Nix package manager
eww - ElKowars wacky widgets
not-os - An operating system generator, based on NixOS, that, given a config, outputs a small (47 MB), read-only squashfs for a runit-based operating system, with support for iPXE and signed boot.
nix-prisma-example - An example Prisma project using nix
nixpkgs - Nix Packages collection & NixOS
nix-config - Personal NixOS configuration
nix - Nix, the purely functional package manager
nixos-beginners-handbook - The missing handbook for NixOS beginners
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
wallpaper-generator - Generate wallpaper images from mathematical functions
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]