Notices by Sergey Bugaev (bugaevc@floss.social), page 2

Announcing aarch64-gnu 🎉
Happy new year!

https://mail.gnu.org/archive/html/bug-hurd/2023-12/msg00110.html

#hurd

Reminder that GNU tar(1) has long options support, so instead of 'tar zxvf' or whatever line noise you can do

tar --extract < my-archive.tar.gz

Polished up my GHurdFileMonitor implementation for glib some more & made a draft MR out of it

https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3626

And then, I went and finally pushed my epoll reworking over the finish line — there was not that much work left, but it had to be done. Once it was, everything fell into place, and now long polls work, short polls work, polls with no interests (basically using epoll as a sleep) work, signals work (including pwait and pwait2 atomically changing the signal mask), and everything seems to just work.

Also apparently my epoll is going into the Hurd upstream soon? Exciting! 🙂

Next, I took my "portable" Wayland patchset and rebased it onto latest upstream main. It's both better and worse; the upstream have done some BSD portability work, so equivalents of some of my changes have effectively been upstreamed, but also they added eventfd usage, so, yay, more things to patch out.

Anyway, so I got Wayland building on the Hurd once again. The tests don't yet pass, I'll need to look into that tomorrow.

After that: Owl, and gtk with its Wayland backend.

wl-clipboard, Owl

There we go! 🏵️

This is Weston's demo clients again — being built with a lot less hacks this time.

#glibc 2.38 is out 🎉

Among other things like strlcpy & strlcat (I know, right?), it includes many fixes and improvements in the #Hurd port, and a brand new x86_64-gnu (aka 64-bit Hurd) port!

https://sourceware.org/pipermail/libc-alpha/2023-July/150524.html

Yet some of my proposed patch sets didn't make it into 2.38, so expect more in 2.39 😉

If you try to use any formatting (perhaps in an attempt to explain your point better), you will be permanently banned from contributing to the project, your instance defederated, and all your previous patches reverted. Moreover, the project's license will be amended to forbid you personally from ever using it.

Not that Mastodon supports formatting anyway, but not even your Pleroma is going to save you, mwhaha 🙃

To contribute to my new project, you must send patches over plain text ActivityPub. That is to say, post them as comments on Mastodon.

And if they don't fit into the 500 characters limit (per patch), then well you should've made your patches more granular; we're not going to bend the rules for you!

Don't forget to set your "email" to your Fediverse handle, like so:
$ git commit --author="Sergey Bugaev <@bugaevc@pixelfed.social>"
and watch your replies for the code reviews!

🙃

@lanodan @a1ba but does it have the 7 lines of copyright header? :D

@a1ba #SerenityOS cat: 49 lines of code

https://github.com/SerenityOS/serenity/blob/master/Userland/Utilities/cat.cpp

@lanodan yes, target triple + some sane (i.e. not just a regex) API to match against it would also be good. And yes "GNU" is problematic for that reason, and also I have no idea what to call the various non-GNU userlands seen on Linux in the wild (as seen in: Alpine, Chimera Linux, OpenWrt...) — just calling each one by its own name is not going to be any useful.

Maybe we should file an issue and write a proposal over at Meson's issue tracker.

@lanodan @abbienormal if (UNIX AND NOT APPLE) you mean, but yeah, I see.

I would argue that that is an OK pattern if they really want to single out Darwin (maybe for Mach-O or something), but not quite right if what they actually care about is freedesktop-ish vs Cocoa-ish. You can certainly have GNUstep on non-Apple systems, and run a regular X11 desktop on Darwin.

@lanodan Meson users too should be aware of this and use it properly, but Meson shouldn't have made it that easy to misuse this.

Like ugh, why didn't they make machine.kernel() and machine.userland() (would return "linux"/"gnu", "linux"/"android", "freebsd"/"freebsd", "freebsd"/"gnu", "xnu"/"darwin")

@lanodan @abbienormal hm, what do you mean, which non-Apple Unix stuff?

@abbienormal but then they return 'android' when Android is detected, even though it too is running on the Linux kernel! You'd then think 'linux' means GNU/Linux then, but no, it still returns 'linux' on non-GNU non-Android Linux systems too.

#Meson needs to learn that Linux is not an operating system unto itself.

No really, like 95% checks for host_machine.system() == 'linux' are wrong, unless you really care about *kernel* specifics like Linux kernel modules. Typically what you want to check is:
- is my compiler GCC / Clang? (use the Meson compiler object for that!)
- is my libc (a recent enough) glibc?
- does this system use a "freedesktop" GUI stack?
- etc etc

> However, if you want to emphasize the presence of systemd by calling the system “GNU/systemd/Linux,” there is nothing wrong with doing so.

Oh hey, so this is a GNU-approved name!