19:49 |
hapax |
http://logs.nosuchlabs.com/log/pest/2025-02-10#1034752 << probably where i got the second missing freedom from |
| |
↖ |
19:51 |
hapax |
|
| |
↖ |
19:51 |
hapax |
|
19:51 |
hapax |
http://logs.nosuchlabs.com/log/pest/2025-02-10#1034756 << really am glad to hear that |
19:51 |
hapax |
http://logs.nosuchlabs.com/log/pest/2025-02-10#1034758 << unfortunately, yeah |
19:51 |
hapax |
|
19:51 |
hapax |
|
19:51 |
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 |
19:51 |
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) |
19:51 |
hapax |
btw how do you manage the filesystem on the second machine? you gotta have libraries/headers there |
19:51 |
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 |
19:52 |
hapax |
http://logs.nosuchlabs.com/log/pest/2025-02-10#1034773 << i'll get in touch over the weekend |
| |
~ 3 hours 5 minutes ~ |
22:57 |
discord_bridge |
(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034789 << Thanks a lot. |
22:57 |
discord_bridge |
(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034788 << We have thought very much along the same lines. |
23:01 |
discord_bridge |
(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034783 << Yep, both ELF and COFF were designed as file-bundles containing constituent files. |
23:02 |
discord_bridge |
(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. |
23:02 |
discord_bridge |
(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. |
23:02 |
discord_bridge |
(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. |
23:05 |
discord_bridge |
(gregorynyssa) * built |
23:05 |
discord_bridge |
(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. |
23:05 |
discord_bridge |
(gregorynyssa) For every assertion made in a man-page two things must be clear: (1) by whose authority/authorship? (2) since when? |
23:05 |
discord_bridge |
(gregorynyssa) Moreover, the man-pages of BSD give examples whereas those of Linux usually do not. |
23:05 |
discord_bridge |
(gregorynyssa) Examples of correct invocations of a given program. |
23:05 |
discord_bridge |
(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. |
23:08 |
discord_bridge |
(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. |