Keyoxide: https://keyoxide.org/9f193ae8aa25647ffc3146b5416f303b43c20ac3

OpenPGP: openpgp4fpr:9f193ae8aa25647ffc3146b5416f303b43c20ac3

  • 7 Posts
  • 29 Comments
Joined 3 years ago
cake
Cake day: November 8th, 2022

help-circle



  • Yuu Yin@group.lttoLinux@lemmy.mlDownsides of Flatpak
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 years ago

    Well; darwin users, just as linux users, should also work on making packages available to their platforms as Nix is still in its adoption phase. There are many already. IIRC I, who never use MacOS, made some effort into making 1 or 2 packages (likely more) to build on darwin.




  • Yuu Yin@group.lttoLinux@lemmy.mlDownsides of Flatpak
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    2 years ago

    When I was packaging Flatpaks, the greatest downside is

    No built in package manager

    There is a repo with shared dependencies, but it is very few. So needs to package all the dependencies… So, I personally am not interested in packaging for flatpak other than in very rare occasions… Nix and Guix are definitely better solutions (except the isolation aspect, which is not a feature, you need to do it manually), and one can use at many distros; Nix even on MacOS!












  • Article 6 of the law requires all “software application stores” to:

    • Assess whether each service provided by each software application enables human-to-human communication
    • Verify whether each user is over or under the age of 17
    • Prevent users under 17 from installing such communication software

    It may seem unbelievable that the authors of the law didn’t think about this but it is not that surprising considering this is just one of the many gigantic consequences of this sloppily thought out and written law.

    That law is a big document; would have been helpful if Mullvad’s article directly cited/referenced as for us to verify some of that.








  • It is because it departs from POSIX that it is good; I recognize the syntax for some functionality is cumbersome and hard to remember though. There are similarities like command names and piping still…

    I use NixOS and home-manager, so for switching I just

      home-manager.users.yuu = {
        programs.nushell = {
          package = pkgs-update.nushell;
          enable = true;
          configFile.source = ../../config/nushell/config.nu;
          envFile.source = ../../config/nushell/env.nu;  
        };
      };
    

    The config.nu and env.nu is basically the default just with a customized prompt.

    Then in my alacritty.ylm I set shell to the nu binary

    shell:
      program: /etc/profiles/per-user/yuu/bin/nu
    

    Also learned from official resources https://www.nushell.sh/book. When I have doubts, I ask either on Nushell’s GitHub discussions or https://matrix.to/#/#nushell:matrix.org

    And to keep a POSIX shell

    {
      environment = {
        systemPackages = with pkgs; [
          mksh
        ];
    
        sessionVariables = rec {
          TERM = "alacritty";
          TERMINAL = "alacritty";
          SHELL = "${pkgs.mksh}/bin/mksh";
        };
    
      environment.shells = [
        "${pkgs.mksh}/bin/mksh"
      ];
    }