minecraft-wayland VS void-packages

Are you using the patched GLFW?

I'm making an attempt to make Minecraft run natively on Wayland using these instructions. One of the steps is to patch libglfw, provided by the glfw-wayland package. I have no experience with compiling xbps packages from source or applying diff patches.

Download the one-nineteen branch and unzip then inside the folder run makepkg https://github.com/Admicos/minecraft-wayland/tree/one-nineteen

for 1.13 and onwards, theres a guide here that makes the game use a patched GLFW version to run (effectively) nativly on wayland with some (if any) performance loss.

Once that's corrected, I think you chose the patch url wrong given that all it is is a README change, which you even filter out. I assume you want the .patches that were committed to the upstream repo?

I followed this guide.

prev: final: { glfw = glfw.override (oldAttrs: rec { patches = oldAttrs.patches ++ [ (prev.fetchpatch { url = "https://github.com/Admicos/minecraft-wayland/commit/ceda97a3f0717050f27093ed2b6682b29415e8d1.patch"; sha256 = "0000000000000000000000000000000000000000000000000000"; excludes = [ ".SRCINFO" "PKGBUILD" "README.md" ]; }) ]; }); }

I have four different .patch-files (from here) in /etc/portage/patches/media-libs/glfw/ and expected portage to automatically apply these patches when emerging media-libs/glfw, but it somehow doesn't.

Already possible.

I was looking for a lightweight OS to run on old Asus Eee PC 1005 HA, which uses a 32-bit Intel Atom N270 processor. I installed Void Linux (https://voidlinux.org/).

I may give DSL 2024 a try and see how it compares.

Linux Void

My computer is running Void Linux and it has only a wired network connection. I can hook up my phone for USB tethering if I need to connect to the WiFi of the ESP32. How do I update the software without downloading some shady programs from filesharing site links on my system? I have the Arduino IDE and the esptool.py script installed.

Classic "everyone is using the software wrong, but it's the fault of everyone, and not the software".

Some distros like Void seem to patch this out.[1]

From mandoc/mdocml's mandoc_char(7) [2]

In roff(7) documents, the minus sign is normally written as ‘\-’. In manual pages, some style guides recommend to also use ‘\-’ if an ASCII 0x2d “hyphen-minus” output glyph that can be copied and pasted is desired in output modes supporting it, for example in -T utf8 and -T html. But currently, no practically relevant manual page formatter requires that subtlety, so in manual pages, it is sufficient to write plain ‘-’ to represent hyphen, minus, and hyphen-minus.

Which is the common-sense thing to do.

Meanwhile, GNU projects become increasingly less relevant due to obnoxiousness like this.

In general the amount of wankery of "the correct hyphen" is staggering.

[1]: https://man.openbsd.org/mandoc_char

[2]: https://github.com/void-linux/void-packages/blob/20c66829134...

So I was about to configure a new Archlinux build on my PC and came across Void Linux. I had already read about it a year ago but never researched it in depth. I know that is a Linux distribution made from scratch, with a different package manager and so on. Void Linux users or people who have tried it, what are your thoughts on it? Do you think the PM is easy to use? what about updates and bugs? what desktop or Tilling Window Manager do you use? could you tell me about it?

Good news about dbus-next: https://github.com/void-linux/void-packages/pull/46760