MoltenVK VS nixpkgs

You could try replacing the wrappers libMoltenVK.dylib found in /Frameworks with the one I’d just uploaded https://github.com/The-Wineskin-Project/MoltenVK/releases/download/v1.2.3/macos-1.2.3-g5cbeaaa-UE4hack-zeroinit-dxvk.tar.xz

Here's the Roguelike third-person shooter Unreal Engine 4 game called Crab Champions that seems to be working thanks to the people who made the UE4 Moltenvk fix (https://github.com/The-Wineskin-Project/MoltenVK/releases).

However, it looks like the latest libMoltenVK (macos-1.2.3-g7b9a415a-UE4hack-Wideline-zeroinit) (huge thanks to Gcenx and nastys/italomandara!) allows the game to work almost perfectly (at least in the few minutes I've been testing).

There’s no need to build MoltenVK from source you can grab prebuilt archives from https://github.com/The-Wineskin-Project/MoltenVK

If this game uses DXVK then try using the following build https://github.com/The-Wineskin-Project/MoltenVK/releases/download/v1.2.0/macos-1.2.0-pr1678-UE4hack-Wideline-zeroinit.tar.xz

You could instead grab an archive from my mirror https://github.com/The-Wineskin-Project/MoltenVK/releases

https://github.com/Gcenx/MoltenVK/releases/tag/v1.1.7 apply these to your crossover and see how it works.

I was testing this version of MoltenVK (Macos_dxvk_patched-1.1.8.tarxz) (https://github.com/Gcenx/MoltenVK/releases/tag/v1.1.8) and I was able to able to get in the game. Before this the game was able to get to the Manu but would just black screen after starting.

The same is true for MoltenVK don’t use the upstream releases/VulkanSDK, instead use https://github.com/Gcenx/MoltenVK

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs

In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].

[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...

[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...

True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)

It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.

That is the problem.

We’ve noticed that some users have been asking about how to use older versions of Terraform in their Nix setups [1, 2]. This is an example of the diverse needs of people and the importance of maintaining backward compatibility. We hope that nixpkgs-terraform will be a useful tool for these users.

I think whateveracct was referring to is this link:

https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...

What that file is doing, is building a package, and it essentially is a combination of what Makefile and what RPM spec file does.

I don't know if you're familiar with those tools, but if you aren't it takes some time to know them enough to understand what is happening. So why would be different here?

#!/usr/bin/env nix-shell #! nix-shell -i bash #! nix-shell -p sops #! nix-shell -I https://github.com/NixOS/nixpkgs/archive/refs/tags/23.05.tar.gz source config.sh "$@"

NixOS just got tabbyml[1] which is built on llama-cpp. Working on systemsd services the weekend and updating latest tabbyml release which supports rocm in addition to cuda

[1] https://github.com/TabbyML/tabby

[2] https://github.com/NixOS/nixpkgs/pull/291744