hapax: http://logs.nosuchlabs.com/log/pest/2025-02-10#1034752 << probably where i got the second missing freedom from
hapax: http://logs.nosuchlabs.com/log/pest/2025-02-10#1034756 << really am glad to hear that
dulapbot: Logged on 2025-02-10 22:03:36 discord_bridge[asciilifeform]: (gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-10#1034745 << It has been very useful to me. (=
hapax: http://logs.nosuchlabs.com/log/pest/2025-02-10#1034758 << unfortunately, yeah
dulapbot: Logged on 2025-02-10 22:05:31 discord_bridge[asciilifeform]: (gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-10#1034748 << The way that LaTeX subsumed TeX, with the proponents of the former using the terms LaTeX and TeX interchangeably in order to bury the advocacy of the latter, was deeply depraved.
hapax: http://logs.nosuchlabs.com/log/pest/2025-02-10#1034769 << reminds me of the pe/coff resource section and the way mswin keeps, e.g., icons for executables
dulapbot: Logged on 2025-02-10 22:44:03 discord_bridge[asciilifeform]: (gregorynyssa) Another idea which I had was to eliminate sparsive packages not by creating one folder per package (as done by GoboLinux and also explicated in your article) but rather by compiling supportive files such as man-pages directly into the executables.
hapax: sounds like a more convoluted way to implement --help though (which i use more often than man pages, through woman in emacs, since i don't even have man(1) installed)
hapax: btw how do you manage the filesystem on the second machine? you gotta have libraries/headers there
hapax: i actually use a similar approach, i don't keep gcc, etc., on a machine i know i'm not gonna compile anything on, so i only move the binaries there, but i keep the directories consistent
hapax: http://logs.nosuchlabs.com/log/pest/2025-02-10#1034773 << i'll get in touch over the weekend
dulapbot: Logged on 2025-02-10 22:47:37 discord_bridge[asciilifeform]: (gregorynyssa) hapax: https://dpaste.org/tfeMo
discord_bridge[asciilifeform]: (gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034789 << Thanks a lot.
dulapbot: Logged on 2025-02-11 19:51:34 hapax: http://logs.nosuchlabs.com/log/pest/2025-02-10#1034773 << i'll get in touch over the weekend
discord_bridge[asciilifeform]: (gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034788 << We have thought very much along the same lines.
dulapbot: Logged on 2025-02-11 19:50:52 hapax: i actually use a similar approach, i don't keep gcc, etc., on a machine i know i'm not gonna compile anything on, so i only move the binaries there, but i keep the directories consistent
discord_bridge[asciilifeform]: (gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034783 << Yep, both ELF and COFF were designed as file-bundles containing constituent files.
dulapbot: Logged on 2025-02-11 19:49:49 hapax: http://logs.nosuchlabs.com/log/pest/2025-02-10#1034769 << reminds me of the pe/coff resource section and the way mswin keeps, e.g., icons for executables
discord_bridge[asciilifeform]: (gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034786 << The --help option is a shorter summary, while the man-page is a longer explanation, even constituting a specification. Both are important.
dulapbot: Logged on 2025-02-11 19:50:09 hapax: sounds like a more convoluted way to implement --help though (which i use more often than man pages, through woman in emacs, since i don't even have man(1) installed)
discord_bridge[asciilifeform]: (gregorynyssa) Aside from providing more information, the advantage of the man(1) system lies in the TUI controls (like the less(1) program by GNU) and searching features.
discord_bridge[asciilifeform]: (gregorynyssa) Also, Sections 2–7 of man(1) under my Linux distribution are edited, bundled, and curated as a single file, whereas Sections 1 and 8 are bulit into particular executables as described above.
discord_bridge[asciilifeform]: (gregorynyssa) * built
discord_bridge[asciilifeform]: (gregorynyssa) Unlike Linux (but more similar to BSD), every man-page (especially under Sections 1 and 8) must contain the version-number of the program, the date of release, and the name of the author.
discord_bridge[asciilifeform]: (gregorynyssa) For every assertion made in a man-page two things must be clear: (1) by whose authority/authorship? (2) since when?
discord_bridge[asciilifeform]: (gregorynyssa) Moreover, the man-pages of BSD give examples whereas those of Linux usually do not.
discord_bridge[asciilifeform]: (gregorynyssa) Examples of correct invocations of a given program.
discord_bridge[asciilifeform]: (gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034787 << Compilation is considered the private activity of a particular user, not a systemic activity.
dulapbot: Logged on 2025-02-11 19:50:33 hapax: btw how do you manage the filesystem on the second machine? you gotta have libraries/headers there
discord_bridge[asciilifeform]: (gregorynyssa) Thus we keep headers and "libraries" somewhere in the personal folder (/home/gregorynyssa for instance) of that user. Moreover there is no need to standardize the names "lib" or "include" or whatever. It should be possible to name the sub-folders anything.