My areas of interest are programming, music, open and free software, open and free federative networks. #Haskell enthusiast. #Xenharmonic / #Microtonal music enthusiast. I value freedom of speech, privacy, and personal freedom in general.
@drq Oof, that list is big. For Nix and NixOS it is just this:
1. Clone the https://github.com/NixOS/nixpkgs
2. Write mostly JSON-like config for your app (a random example https://github.com/NixOS/nixpkgs/blob/808a8f52dce6e33270ab00472810687dbcca2eca/pkgs/applications/networking/instant-messengers/psi-plus/default.nix )
3. Make a merge request
@drq I’m writing this message from a NixOS machine (I have few that I easily synchronize just by “git pull && nixos-rebuild switch”). And recently I did a major release update on my machines, and that release didn’t wreck my OS installation like it happens sometimes with other distros. It went just perfectly fine. And I still have an old derivation, I could just boot to the older version of my system with no problem and interference with current one. It works and it’s awesome.
@drq
> I see somebody using Nix, it's always something isn't working
I only hear this from someone who doesn’t use Nix. For me it’s like a horror you tell kids to make them behave good.
For me it was working from the beginning. And it was doing what I wanted (actually I wanted something like Nix for years before I even get to know it exists). And it was working for me for around 2 years already. Since now you saw me, you can remove “always” from your notes.
@drq Could you describe steps for each you have to go through in order to add a new package to the repository?
@archer72 Depends on how big your account is initial sync can take a while. It can take around 20 minutes with no problem. But Element usually does this faster because of room members lazy loading I suppose. So it technically should take just a minute or two. But you still have to wait.
Having fun with #OpenGL #GLSL shaders. Rendering #MandelbrotSet and moving/zooming around it. You can play with it too:
@temporal@mastodon.technology I use only #NixOS (except maybe Android on my smartphone if that counts, Mobile NixOS is still in development) every day for around a year and a half. I use it even on my small Raspberry Pi 3B+ server. Was the best choice I made, and I see no alternatives on the horizon. VMs, Docker containers (which can also be powered by Nix), gaming, you name it. Not sure about Windows though, haven’t used it for a decade. P.S. A VM per project is a heavy overkill. Nix does a lot better job.
@Main_Tomato@mas.to there is “low priority” tagging and “historical” rooms list. Maybe either one could work for you.
@farseen@social.linux.pizza @karmanyaahm binary packages can be used as well. Some depend on FHS (NixOS is not FHS-compliant), there are helpers for simulating FHS. That’s how Steam is packaged for NixOS.
Here are some links to show examples of how this can be done:
https://nixos.org/manual/nixpkgs/stable/#sec-fhs-environments
https://nixos.wiki/wiki/Matlab
https://github.com/jorsn/matlab-nix-imperative/blob/master/default.nix
@farseen@social.linux.pizza @karmanyaahm Take for instance a random C++ package based on CMake and see how is it “packaged” in Nix:
Or here is my own example of C++ project where I just call plain “make” commands in the building and installation phases:
https://github.com/unclechu/cpp-parser-experiment/blob/4748aaed/default.nix
@farseen@social.linux.pizza @karmanyaahm I don’t know how many packages AUR has. According to https://search.nixos.org/packages there are more than 80 000 packages at the moment.
It’s not a big deal to “package” something in Nix. You are just writing a *.nix file which in best scenario just looks like a JSON file. You can take existing packages with similar build tooling as a reference. “nixpkgs” (the default Nix helpers and packages collection) provides a lot of helpers for different languages and build tools.
@karmanyaahm just start using Nix under your Arch, get familiar with it. That’s how you can have both. NixOS just moves you one step forward from Nix. Not only your projects are supplied with dependencies by Nix, but also your whole system. Your “installed packages”, your Xorg config customization, network config, firewall rules, drivers setup, realtime kernel patch, etc. As well as your home directory configs (see Home Manager). But nothing stops you from using just Nix under your distro.
@karmanyaahm I would recommend it, start playing with it and getting familiar with it right now. And then the transition would be much easier. At least that how it was for me.
By the way, take benefits of reproducibility, configure your NixOS in a virtual machine inside your Arch and then just take this config and replicate it on your real hardware (with minor hardware-specific adjustments). That would be a fun experience, to see the actual magic.
