Inbred: chaorace’s family has been a bit too familiar. (Can be inherited)
Expand?
- 1 Post
- 3 Comments
0·1 year agoI’m a plaintext git patch sent via email and lost in the maintainer’s spam folder
Unfortunately, kbin instances are unavailable via Lemmy right now due to hosting problems on kbin’s side of the equation (see Kbin Codeberg #101). This will probably be fixed soon, so keep an eye on that issue for progress.
Even if it were working, however, there’s actually something of a required ritual that you’ll need to go through when subscribing to an external community which your instance is not already federated to (i.e.: communities where nobody on SDF is currently subscribed). Here are the steps you’ll need to follow:
- In the community search, paste in the following pattern:
!community@instance.domain(e.g.:!technology@beehaw.org) - Press [Enter], wait for the search to finish (it’s normal to see no results)
- Wait a few minutes
- Refresh the search page and search for the common name this time (e.g.: “Technology”)
- The community should appear and be available for subscription now
FWIW: There are plans to improve this unintuitive workflow in the future (see Lemmy Backend Github #2951).
If these steps don’t work, it’s possible that the community may simply be too new. You’ll sometimes need to wait an hour or so after a community has been created for it to start being available on external instances.
- In the community search, paste in the following pattern:
You may be interested in reading this post about the process of packaging Steam.
tl;dr: It’s mostly an annoyance reserved for packagers to deal with. Dynamically linked executables can be patched in a fairly universal fashion to work without FHS, so that’s the go-to approach. If the executable is statically linked, the package may have to ship a source patch instead. If the executable is statically linked & close-source, the packagers are forced to resort to simulating an FHS environment via chroot.