waymonad VS nixpkgs

I am personally waiting for Waymonad. https://github.com/waymonad/waymonad

It takes time, but the teams behind wlroots etc are doing good work to make sure that wms managed by smaller teams can exist. There are even clones for your specific wm on wayland. See https://github.com/waymonad/waymonad

In addition, there was the last commit in 2019. Thus, it can be assumed that the project is dead and therefore nothing will change on the current state. And according to https://github.com/waymonad/waymonad/issues/44, there are probably not enough people who would actively participate in a fork.

Ideally xmonad would be ported/xmonad devs would be working on waymonad, but I doubt it will happen. Waymonad seems to be abandoned.

Nice to see Qtile on Wayland. But I'm personally waiting for xmonad on Wayland.

https://github.com/waymonad/waymonad

I wouldn't count on it, as Waymonad has not seen active development since 2019 and the Haskell bindings to wlroots have not been updated since 2019 as well. There is a fork, but it has not been active since September 2021. Also, it was based on wlroots, not sway.

That's what the XMonad fans are using: https://github.com/waymonad/waymonad lets you write your Wayland compositor in Haskell, is analogy to the way XMonad lets you write your X window manager in Haskell.

Unfortunately it was abandoned https://github.com/waymonad/waymonad/issues/44

regarding keeping an interest, waymonad has been dead for something like two and a half years but according to startrack it's still getting people giving him stars so i don't think you should worry about it.

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