igorlogius

I forsee the creation of another arch based distro that is specifically designed for vegans that will solve this problem

not really an issue with a few more lines of configuration

nix.gc = {
    automatic = true;
    dates = "weekly";
    options = "--delete-older-than 30d";
};

https://nixos.org/

well, with stuff like this i meant dpkg-reconfigure, since i switched to nixos where configuring and setting up basically means adding/editing a couple of lines in /etc/nixos/configuration.nix. For automatic system updates for example, i just had to add: system.autoUpgrade.enable = true; and done. Nicest way to configure and manage a system i’ve experienced yet.

Kind of glad i dont have to worry about stuff like this anymore, but i do sympathize as a former debian user.

valid argument - maybe jq isn’t always the best tool for the job … but i personally been happy with using it

insert uninstall bootloader meme

piping JSON

https://github.com/jqlang/jq is a good option to deal with this

eh … that plugin is likely easiest to install via your distros package manager … you dont have to compile it from source

edit: i was actually thinking about a different plugin: https://docs.xfce.org/panel-plugins/xfce4-netload-plugin/start

I migrated recently and am pretty happy with it. Once you have everything in configuration.nix setup, its like you dont even need to think about your system anymore if you dont want to. Everything just works and will continue to work and can even easily be replicated onto another system in case of hardware failure. Just make sure to keep your /home on a seperate nas/raid/drive and a backup of your configuration and hardware.nix and your golden.

our Lord And Savior NixOS

https://mynixos.com/nixpkgs/option/system.autoUpgrade.enable

#amen

There are a few runtimes which provide quite a few things already (for desktop and system integration) and there are a growing number of modules for other commonly used stuff, example ffmpeg (de/encoding) which other flatpaks can reuse. Also flatpak uses OSTREE to try and prevent duplication.

The more the devs work with it the better their packaging and bundeling is gonna get. At the moment it is new and they have to re-learn some things and not everything might be done in the best way possible, but that will improve with time.

And i think it benefits everyone. Devs and distro maintainers dont need to repackage, test and integrate stuff for all distors and users have stuff that has an almost 100% chance of working out-of-the-box that is also quicker with updates/fixes.

IMO, overall an improvement in comparision to the current state with deb/rpm/pkgs/… for userspace applications.

planning an ‘All Snap’ desktop next year.

I wonder where all the users are gonna migrate

Yes, its not the “common” way to use it. But i think it works well enough, but just to be save i added some annotations.

90% of blocked bugs

human: developer
ball: bug  (report)
dog: (reporting) user

annotations are “spoken/thought/done” by the human.

maybe “OpenSuse tumbleweed” ?

refs.

• https://www.opensuse.org/#Tumbleweed
• https://distrowatch.com/table.php?distribution=opensuse

deleted by creator

deleted by creator

Thanks for the info :) +1