The product of a chat with @QuazarOmega@lemy.lol

  • onlinepersona@programming.dev
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    3
    ·
    6 months ago

    Still haven’t reached the flakes stage. An experimental feature that the maintainers are too afraid to treat as experimental and make breaking changes, but unwilling to name stable because it requires bug-fixes and changes that would be breaking, but too afraid to break because… reasons.

    Anti Commercial-AI license

    • grue@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      6 months ago

      [rest of post]
      Anti Commercial-AI license

      Hey look, the trend is spreading: you’re the second user I’ve seen doing that.

      It’d be nice if the Lemmy devs added some sort of metadata field to support that so that (a) we could have a preference to insert it into every new comment automatically, and (b) it could be reduced to a badge on the comment header or something so that it would be less obtrusive to those of us who aren’t trying to do anything that would require us to pay attention to it.

    • Shareni@programming.devOP
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      6 months ago

      It’s pretty easy for home-manager use, but still really useful. You can:

      • choose which packages to install from stable and which from unstable
      • add packages from repos that have flake.nix in them
      • correctly match nix and home-manager versions, and always update them at the same time
      • allow-unfree without nixpkgs conf, so 1 less directory required in .config (if they accepted the “experimental” features it’d be down to 1)

      Here’s an example:

      flake.nix
      {
        description = "home flake";
      
        inputs = {
          nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
          home-manager.url = "github:nix-community/home-manager/master";
          home-manager.inputs.nixpkgs.follows = "nixpkgs";
          nixpkgs-stable.url = "github:nixos/nixpkgs/nixos-23.11";
      
          # nixgl.url = "github:guibou/nixGL";
        };
      
        outputs =
          {
            self,
            nixpkgs,
            nixpkgs-stable,
            home-manager,
            # nixgl,
            ...
          }@inputs:
          let
            system = "x86_64-linux";
            pkgs = import nixpkgs {
              system = system;
              config = {
                allowUnfree = true;
              };
            };
            pkgsStable = import nixpkgs-stable {
              system = system;
              config = {
                allowUnfree = true;
              };
            };
          in
          {
            homeConfigurations = {
              shareni = home-manager.lib.homeManagerConfiguration {
                inherit pkgs;
                modules = [ ./home.nix ];
                extraSpecialArgs = {
                  inherit inputs;
                  inherit system;
      
                  kmonad = pkgsStable.kmonad;
                };
              };
            };
          };
      }
      
      • PuddleOfKittens@kbin.social
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        6 months ago

        The ‘code’ tag here does not respect newlines, I tried to fix it but this is the best I could do:

        `{ description = “home flake”;

         inputs = {     nixpkgs.url = “github:nixos/nixpkgs/nixos-unstable”;
        
         home-manager.url = “github:nix-community/home-manager/master”;
        
         home-manager.inputs.nixpkgs.follows = “nixpkgs”;
        
         nixpkgs-stable.url = “github:nixos/nixpkgs/nixos-23.11;
        
          # nixgl.url = “github:guibou/nixGL”;
        
        

        };

        outputs =     {
        
           self,
        
           nixpkgs,
        
           nixpkgs-stable,
        
           home-manager,
        
           # nixgl,
        
           …
        
         }
        
        

        @inputs:

         let
        
           system = “x86_64-linux”;
        
           pkgs = import nixpkgs {
        
             system = system;
        
             config = {
        
               allowUnfree = true;
        
             };
        
           };
        
           pkgsStable = import nixpkgs-stable {
        
             system = system;
        
             config = {
        
               allowUnfree = true;
        
             };
        
           };
        
         in     {
        
           homeConfigurations = {
        
             shareni = home-manager.lib.homeManagerConfiguration {
        
               inherit pkgs;
        
               modules = [ ./home.nix ];
        
               extraSpecialArgs = {
        
                 inherit inputs;
        
                 inherit system;
        
                  kmonad = pkgsStable.kmonad;
        
               };
        
             };
        
           };
        
         };
        
        

        }`

    • Shareni@programming.devOP
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      6 months ago

      That’s such a bad name, I only see lixmaballs.

      How do you like it, that’s one of the earlier forks, right?

  • nickwitha_k (he/him)@lemmy.sdf.org
    link
    fedilink
    arrow-up
    4
    ·
    6 months ago

    I’m going to have to come back to Nix/NixOS in a bit. I tried setting it up as a baremetal OS but clearly didn’t have sufficient understanding of the Nix DSL to get it to do what I want. Following the instructions in the manual led to a functional system missing the network stack. I’ll probably wait until the official docs catch up as it appears that they are quite a bit behind. That and I’m not sure how I feel about a DSL for package management. I’d much rather use JSON or YAML, or even INI or TOML. Maybe if I were a LISP or Haskell guy.

    So, after a few hours sunk there, I switched to Fedora Silverblue, which worked out of the box and added Incus via rpm-os-tree. Just need to get the UI setup and I can start moving through my distro list.

    • Shareni@programming.devOP
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      6 months ago

      I’m going to have to come back to Nix/NixOS in a bit.

      Use nix + home-manager first for sure. It’s far easier, and you can slowly get into it while making a list of bleeding edge packages.

      I’ll probably wait until the official docs catch up as it appears that they are quite a bit behind

      Skip them altogether when you’re starting out. I gave up on trying nix the first few times due to how bad they are. zero-to-nix.com is better for learning the basics of nix.

      That and I’m not sure how I feel about a DSL for package management. I’d much rather use JSON or YAML, or even INI or TOML.

      The closest you can get is home-manager with a list of packages in a json-like format. It’s really not practical to develop a declarative system without a programming language. A basic example would be variables, more advanced would be to write a wrapper that modifies the package so it automatically runs the required cli commands to use your dediated gpu and nixGL with specific packages (nvidia-run-mx nixVulkanNvidia-525.147.05 obs for example).

      It’s sort of like IaC where you’ve got terraform (dsl), pulumi (various languages), and cloudformation (json/yaml). Can you guess which one is universally despised?

      Maybe if I were a LISP or Haskell guy.

      Then you’d use guix and a dsl made within an actual programming language (much better approach IMO).

  • QuazarOmega@lemy.lol
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 months ago

    The product of a chat with @QuazarOmega@lemy.lol

    Can confirm, very productive indeed ;)

    There is only a way forward, and once you start, you cannot stop