Aiwendil

Just to make this clear (Sorry if it's unnecessary, but maybe still useful info for others)...Path= lines in .desktop files are not related at all to the $PATH environment variables. They do something completely different (And yes, picking Path as key was a terrible choice in my view). Path= lines in .desktop files change the current working directory...they do about the same as a cd <directory> in a shell.

They do not change where a .desktop file looks for executables....only indirectly if a executable runs another file relative to the current directory or looks for images/icons/audio/other data relative to the current working directory.

And I have no clue why it doesn't work with TryExec...the desktop file spec doesn't mention anything about that :( ( https://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html )

Try adding a PATH=/home/werecat/Grayjay line to your .desktop file. Without it the application will run with your home directory as your working-directory...and there the data files are missing (Why you need to copy them to your home). The path entry makes the program work in /home/werecat/Grayjay where the data directories actually are.

Edit: That is assuming when you started it manually you did a cd Grayjay and a ./Grayjay or similar. So you changed your working directory there first before starting it. If that is not the case ignore my post ;)

"Timber!"

I remember playing this some years ago...it was a lot of fun. Back then the "Atlantis" (I think...not sure, its been some years) campaign wasn't completely finished so maybe time to give it another shot :).

Obscure as in "only for a very specific purpose and nothing else"?...

Well, there is the Mircrosoft linux distro for their azure cloud

I guess DD-WRT as distro for router is also kind of obscure. Or the more general openWRT for embedded systems.

I imagine the "update from another system" path runs in troubles with more complex gentoo installs than just the base system. For a full update from the live disk it will have to include lots and lots of (often exotic) tools that might be used in the building process (document generators like doxgen, lexer, testing frameworks, several build systems and make-likes. programming languages...) in addition to being able to build against the already installed updates for packages while not accidental building against packages that are not updated yet.

Or you go the simpler way and only do a base update from the live-system...only update the base build system and package management of the gentoo system and afterwards boot in a "broken" system in which only the basics works and rebuild it from there.

For be both those options sound less desirable than what is suggested in the blog.

Cautionary

I settled with German because finding English took way longer than I care to admit ;)

http://divajutta.com/doctormo/ubunchu/c.html

here you go ;) (well, not really a translation of what OP linked but the first chapters of the manga in....lots of different languages)

As much as I dislike snaps..it's not true that everything snaps do can also be done with flatpaks. snaps can be used for system updates (system libs, kernel, drivers...)..something flatpaks can't do (and are not meant to do). (Sorry, best link I can find in a short search...but it doesn't get in very many details :()

Isn't that what's the articel about? An alpine contributor calling out projects that "supposedly" target linux according to themselves but instead only target gnu/linux.

As gentoo user I can't argue with that... ;)

But I think there are reasons why someone would want to build suckless tools manually...namely that their configuration is mostly done in the source-code (Damn, it's so hard to not write anything too opinionated about suckless but I really try my best). But even then I agree with your other post that it's far better to use the distro facilities for building the the distro source packages just with your own patches applied.

Lets set aside my personal belief that suckless is a satire that too many people started to take seriously...

Always using the latest git version as done in the article doesn't strike me as the most sane thing to do if you "just" want to use the software especially as suckless offers version tarballs.

But suggesting sudo make clean install to build is really not okay...(and also not how the suckless tools I checked suggest it). You cloned (or better extracted the tarballs) as user...there is not a single reason to build the software as root. If you have to install then do it in two steps, build as user and only "make install" as root.