nixos-homepage
flatpak
nixos-homepage | flatpak | |
---|---|---|
5 | 431 | |
275 | 4,063 | |
1.1% | 1.0% | |
9.3 | 9.2 | |
7 days ago | 1 day ago | |
Astro | C | |
- | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nixos-homepage
-
Please provide the commandment to install NixOS within executable scripts rather than as mere text.
If you care, there won't be any substitute for keeping track of changes to the recommended install and deciding whether you do or don't want to follow suit. Luckily, the site's source is public: https://github.com/NixOS/nixos-homepage/blob/master/download.tt
- Nix OS -> Learn -> How it works is broke on the website
-
Bottles: Easy GUI front end to run Windows software on Linux
Wow! I can't believe I've never noticed that. For many years, the only graphical installation disk was based on Plasma, and I think it also had that tag. NixOS only started shipping a GNOME iso for installation purposes a little over a year ago (for 20.09), and I kinda never noticed.
Looks like the main reason GNOME is recommended for installation media at the moment is that it does a better job of autodetecting HiDPI displays, and then scaling appropriately: https://github.com/NixOS/nixos-homepage/pull/643
There are also some packaging issues for Qt with NixOS, because Qt plugins fundamentally rely on ‘impurity’ at runtime, and the Qt framework makes promises it doesn't keep about binary compatibility.
Here are some of the relevant issues for historical context and some of the tradeoffs Nixpkgs developers have faced when it comes to handling Qt and KDE packaging:
https://github.com/NixOS/nixpkgs/issues/86369
https://github.com/NixOS/nixpkgs/pull/54525
https://github.com/NixOS/nixpkgs/pull/44047
I realize that may not be a fully satisfying answer as to why the GNOME-based installation graphical ISO is recommended over the Qt one because one can imagine that the Qt packaging issue should be resolved some other way, or see the difficulty of packaging Qt plugins and applications in Nixpkgs as fundamentally a Nix defect. But I hope it makes that decision make more sense.
FWIW, afaict Plasma is the more popular of the two major DEs on NixOS, and it's what I've always used on NixOS myself, including now. It is definitely usable.
-
Download NixOS, sha256sum dosent match
Looks like there's already a related issue: https://github.com/NixOS/nixos-homepage/issues/745
flatpak
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Podman Desktop 1.6 released: Even more Kubernetes and Containers features
No, it looks like you have to do it on an application basis.
https://github.com/flatpak/flatpak/issues/2913
- how strong is the steam (runtime) sandbox for games?
- Flatpak 1.14.5 Released
-
Been thinking of switching to linux but I am a noob
Flatpak
- FLaNK Stack Weekly for 20 Nov 2023
-
Flathub – The Linux App Store
> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections.
nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions.
That is what Flatpak does. It is Flatpak itself that makes the network connections.
https://github.com/flatpak/flatpak/blob/main/completion/flat...
Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.
- How to prevent/allow chrome from accessing network devices?
-
Linux Phones (2022)
The only performance impact I know of is with the seccomp filter in CPU-bound tasks: https://github.com/flatpak/flatpak/issues/4187
Skimming through the recent comments, there might be a way to optimize some of it.
What are some alternatives?
lutris - Lutris desktop client
steam-runtime - A runtime environment for Steam applications
Autodesk-Fusion-360-for-Linux - This is a project, where I give you a way to use Autodesk Fusion 360 on Linux!
firejail - Linux namespaces and seccomp-bpf sandbox
Homebrew-cask - 🍻 A CLI workflow for the administration of macOS applications distributed as binaries
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
programs - Repository for programs installation
nix-gui - Use NixOS Without Coding
SDL - Simple Directmedia Layer
com.valvesoftware.Steam