• Auli@lemmy.caEnglish
    491·
    1 年前

    What’s bloat? You need to have a functional computer.

  • Clipper152@lemm.eeEnglish
    11·
    1 年前

    Stuff that’s helped me so far:

    • sudo paccache -r
    • ncdu ( you may have to install it first )
    • pacman -Qqdt
    • Konmari’ing my computer occasionally.
  • snor10@lemm.eeEnglish
    9·
    1 年前

    I have this problem with Tubleweed. Installed a few DEs to try them out, but it was easyer to install than remove the same swathe of packages. Now I have multiple file browsers and settings programs :(

  • Rafael D Martins@lemmy.eco.brEnglish
    102·
    1 年前

    That’s why I miss Gentoo so much. Nothing handle packages like Portage does!!

    But… The compilation times made me migrate to Fedora…

  • redcalcium@c.calciumlabs.comEnglish
    81·
    1 年前

    Buy a new, bigger ssd and start again from scratch. Copy your data from the old disk, then retire it into your NAS to add storage there. Repeat every once in a while, and suddenly your nas is big enough to qualify as a homelab.

    • Vuraniute@vlemmy.netOPEnglish
      11·
      1 年前

      Right now I have a VM running NixOS, so I can figure things out. What annoys me is that when asked to list all the programs I want to use, I struggle, but installing things on the fly is so much more easier. Nix-env does that, but it doesn’t add it to a /etc/nixos/configuration.nix, does it? Also, I know about home-manager, but I’ve heard it’s extrememly difficult.

      • Laser@feddit.deEnglish
        4·
        1 年前

        No, nix-env installs to your user environment, which the nixos-rebuild command barely touches. It doesn’t touch the global configuration file. In fact you can even manage user accounts imperatively.

        My approach is the following: try a program using nix run (or nix-shell, depending on the case) and if it does what I want, add it to my configuration and nixos-rebuild test. It will then be available permanently on next update.

        What I also do is keep all nix-related files in a git repository under main user control and have the flake.nix (if using flakes, otherwise configuration.nix) soft linked into /etc/nixos. This also enables rollback on your configuration, not only on the actual system state.

        I agree that each package takes more time, but OTOH, you save a lot of time and effort in the longer run. Also I don’t really have that high fluctuation of packages that it actually matters.

        home-manager is a bit in a weird spot in my opinion as in it’s not very clear how it should be installed. If it’s a NixOS module, your changes will only be applied during rebuild - which only root can trigger. But if you’re already triggering those as root, you might as well as the packages globally. I generally install globally and configure the options using home-manager.

        • Vuraniute@vlemmy.netOPEnglish
          11·
          1 年前

          Sounds great, but I don’t like editing a config file every time I want to install an app,.

          • Laser@feddit.deEnglish
            6·
            1 年前

            Alright, if that’s too much of a hassle you shouldn’t switch. I’m unaware how to do all of that in one step on the command line. All I can say is that the last time I added programs to the array was two weeks ago. So the workload is negligible… on the other hand, on Arch, when installing something new that you then decide not to keep, you need to track the dependencies that you no longer need (pacman -Rs $(pacman -Qqdt)) if I’m not mistaken.

            Also, the amount of work saved depends on what you’re installing: let’s say you install OpenSSH on your machine. On NixOS, that’s editing about six lines in my configuration and then rebuilding. On Arch, that’s

            1. installing OpenSSH (pacman -S openssh)
            2. Editing /etc/ssh/sshd_config
            3. Editing your firewall settings (This happens automatically on NixOS)
            4. Enabling and starting the OpenSSH service (NixOS does this for you)
            5. Applying your changed firewall rules (again, automatically on NixOS and guaranteed to be correct)

            So you have double the configuration files to be edited and triple the commands to be ran, while during all of this, nix actually does the thinking for you (e.g. you change a port in your OpenSSH config -> the firewall configuration is updated automatically).

            • Vuraniute@vlemmy.netOPEnglish
              11·
              1 年前

              Sounds neat. I am really considering NixOS, that’s why I’m asking for advice here. It really sounds like a nice and more convenient distro. Sadly, I still haven’t figured out how to make my own builders, even after Nix Pills. Thankfully, programs like crate2nix exist.

    • nicoty@lemmy.mlEnglish
      11·
      1 年前

      You can use Nix outside of NixOS. Nix + Void has been the mainstay for my machines for the past couple of years.

  • nomadjoanne@lemmy.worldEnglish
    51·
    1 年前

    It’s inevitable. Occasional needs come up, so you install stuff and forget you have, or you think, “Well, I won’t remove that because I might need it at some point in the future.” Reinstalling every couple of years is not a bad thing. Just make sure to save your home directory.

    • Vuraniute@vlemmy.netOPEnglish
      01·
      1 年前

      Generally when over time you start installing more and more stuff and you forget to remove it and it feels clunky and bloated.

      • ElectroLisa@lemmy.blahaj.zoneEnglish
        2·
        1 年前

        pacman -Qs, and look through packages you don’t need and delete them. Then you’ll hit a dependency, and another one, and another… and you’ll find out one app requires the gtk3 package so like 20-30 packages are just for it and can’t get deleted

    • Vuraniute@vlemmy.netOPEnglish
      11·
      1 年前

      I installed SwayFX, but no program wanted to open in Wayland despite XWayland being installed, complaining about “no x server”, even the wayland-native programs. I gave up and went to XFCE4, then back to SwayFX because Wayland magically started workinng.