epub-create VS guides

It's in the repo i linked to upthread; in particular, please refer to this file at this commit, with the four instances of cat ${SPINE} | replaced with <${SPINE}[a].

In my own case, although i'm not active on any microblogging platform, i am a FOSS dev and, er, 'documenter', and i recently read up a bit on the EPUB standards to put together a guide and shell script for creating a minimal EPUB.

Last year i encountered a problem caused by LVM's build system relying on a bashism. And i recently release a simple shell script for creating EPUBs, which tries to avoid using non-POSIX functionality so that it's more likely to be usable on different systems/platforms.

i can reproduce this on my system, using my epub-create script i released just the other day. :-)

In the context of the Ruby snippet you shared, the indentation doesn't matter for what the code is doing, but in other contexts, the indentation *can( matter. For example, i recently wrote a shell script to create a minimal EPUB, which uses heredocs to create XML and XHTML files. If Emacs indented the 'headers' and 'footers' according to their position in the code structure, their indentation in the resulting files would be misleading (even though this wouldn't affect the validity of the markup).

i agree with this piece, as someone who likes man pages to the extent of having ported significant amounts of the s6-ecosystem docs to mdoc(7), and as someone who has also written a number of guides.

And the -bin kernel can be used to easily get many of the settings you'll need when you build your own kernel.

Gah, didn't even consider that the OP might have meant the cover image! Probably at least partly because i know that EPUBs don't necessarily need a cover image - i learnt this as a result of learning how to create a minimal EPUB. (And i actually have many EPUBs without a cover image.)

The point is to be able to customise where you want/need to, and to not have to when you don't. The -bin packages for FireFox, LibreOffice and Zig meet my needs, so i use them. i used the -bin package for the kernel to help me create a minimal kernel for my hardware, because messing around with kernel configuration is not my idea of a good time. But more generally, compiling allows me to specify things like: "i want packages compiled with USB and PCRE support where available, but i don't want them compiled with GNOME support."

Even though D-Bus is probably most often encountered by people in the context of GUI sessions, it's not specific to that; it can be (and is) used outside of such contexts. The widespread misunderstandings i've encountered about D-Bus over the years led me to write a short guide, "D-Bus: the essentials".

(Some related background you might find helpful: a guide i wrote about D-Bus and X sessions).

But more generally, you might find it helpful to refer to this guide i wrote on creating a minimal Gentoo-patched kernel via gentoo-kernel-bin (which can then be regularly updated just like any other Gentoo package).

Take advantage of savedconfig where appropriate, e.g. for kernel builds. In particular, this can be used to easily create a minimal kernel for your hardware.

(Further to this, you might be interested in my guide to creating a minimal kernel for your hardware.)

[a] i've actually written a quickstart guide to writing man pages with mdoc(7), to try to encourage others to use the semantics-oriented mdoc(7) macros for man pages, rather than the presentation-oriented man(7) macros.