A fundamental piece of #aux is the core package set. These packages are vital to the project and are used by all other areas of the ecosystem. If you have the expertise working with #nixos / #nixpkgs, please consider joining us!
It’s so annoying if you have to rely on faulty hardware: Everytime I want to type lib.pipe I first type lip.pipe. I only notice when nix complains. Only happens with pipe, because it starts with p I assume.
After a few months of maintaining my crafts-flake project, I just landed the final PR upstream in #nixpkgs which means that #rockcraft, #charmcraft and #snapcraft willl soon be readily available to all #NixOS users 😎 🚀
Thanks to @delrothhttps://github.com/delroth/grep-nixos-cache/ and the following YARA rule [0] I have been able to check all the current #nixpkgs unstable Linux x86_64 packages available in cache for the known liblzma backdoor payload: no match 🎉
My main goal was to identify packages built from binary sources that might be using it.
It is nice that doing investigations like that is accessible to individuals and fast to do. It can even be useful to a wider community than just #NixOS
I've now included a separate security section, an about page, a link to the rss feed, and added a note above the auto-generated posts to explain how they were created. Please let me know if there is anything else that would be useful!
Can any #nix nerds tell me how a "nix-native" program would handle configuration? If the primary way to configure my app is with a configuration.nix files, what is the best way to pass that configuration information to the app? Can the app just read the nix store directly somehow? Or would it need to write the config to a file which the app would read? Thanks in advance 😁
When you use nixpkgs do you neglect the regular cabal setup (like cabal freeze)? Do you not pay much attention to people who aren't using nixpkgs for your project? Or do you try to make it work well without nixpkgs too?
Okay, so, when I install #Nix on another #Linux distro, in single-user mode (just to be able to build/install #Nixpkgs because the distro ships ancient stuff), is there a way to declaratively (in my dotfiles for example) list packages I'd like to have installed and then on every new machine just run a single command to install them all, or, if the list has changed, do the necessary changes to install/update/remove packages as required? Or do I only get that feature with #NixOS?
It is a bummer that the only way to get #rstats on #Manjaro is through AUR. I have nothing but bad experiences of AUR in Manjaro, even if something works initially, it will break eventually.
I would love to have it in the Manjaro repos or as a #flatpak. It is officially available for #Linux on Ubuntu/Debian, Fedora and OpenSuse, so it ought to be possible.
On a related note, how difficult is it to turn a .deb file into a flatpak?
If you wanna try it (and have Flakes enabled), you can simply run the following command:
nix run github:blinry/nixpkgs/tic-80#tic-80
Let me know if something breaks! :D Would be happy about feedback or code review in the PR! Haven't tried or enabled it on MacOS, if you wanted to try that, that'd also be wonderful! #nix#nixos#nixpkgs
How much of a stupid idea is it to use the packages from #nixpkgs and use them on #ubuntu 🤔?
Probably doesn’t make much sense when I have to recreate all the services and such.