Waffelson@lemmy.world to linuxmemes@lemmy.world · 7 months agoIn search of a non-existent thinglemmy.worldimagemessage-square82fedilinkarrow-up1400arrow-down117
arrow-up1383arrow-down1imageIn search of a non-existent thinglemmy.worldWaffelson@lemmy.world to linuxmemes@lemmy.world · 7 months agomessage-square82fedilink
minus-squareVincent Adultman@lemmy.worldlinkfedilinkarrow-up6·7 months agoThat’s my goal. When I tried NixOS 3 years ago I didn’t had time and there was a lack of documentation to make a .nix for missing packages. Community was… something not very welcoming. I will try again during college break.
minus-squareJohanno@feddit.delinkfedilinkarrow-up3·edit-27 months agoWell documentation is still not great. But I can deal with it. The first step is to really understand how nix works and how nix-shell -p works. Then probably know that autoPatchelfHook exists And sth. You have to watch out for if you install sth. With a daemon or a service you need to enable it additionally to the installation. So for example for open-iscsi you need to enable the service.open-iscsi = enable so it can work. Flakes are still a nogo for me. I don’t understand them and I don’t want to deal with them until I get the rest into my head.
That’s my goal. When I tried NixOS 3 years ago I didn’t had time and there was a lack of documentation to make a .nix for missing packages. Community was… something not very welcoming. I will try again during college break.
Well documentation is still not great. But I can deal with it.
The first step is to really understand how nix works and how nix-shell -p works.
Then probably know that autoPatchelfHook exists
And sth. You have to watch out for if you install sth. With a daemon or a service you need to enable it additionally to the installation.
So for example for open-iscsi you need to enable the service.open-iscsi = enable so it can work.
Flakes are still a nogo for me. I don’t understand them and I don’t want to deal with them until I get the rest into my head.