forked from extern/nix-config
d61e7b8a31
Although this was cool, it created some inconveniences that I'd rather not have to deal with. For example, opening a document required manually copying the file to the container mount first. Instead of containerizing a subset of GUI applications, it's likely much easier and more effective to spin up a virtual machine of the current system. That way all GUI applications benefit from virtualization and not simply containerization, which caused issues when certain programs detected that they were already open from the wayland socket. A final benefit of this change is that which container an application is running in is no longer ambiguous. Although it was possible to use custom GTK themes depending on which container an application belonged to, containers for system-installed applications tend to bring a large amount of overhead. Only using containers for applications that deal with untrusted inputs and have a large attack surface seems better in this case. |
||
|---|---|---|
| .. | ||
| default.nix | ||
| dev.nix | ||
| iamb.nix | ||
| rar.nix | ||
| srb2.nix | ||
| wine.nix | ||