6 ms·
> So what we are missing now is a 500GB framework that can write the config file for the programming language that is writing a config file for the actual progr
by Bost 3y ago
> So what we are missing now is a 500GB framework that can write the config file for the programming language that is writing a config file for the actual program I wish to use.
That exists since 1960. It's called LISP. The e.g. https://guix.gnu.org/ https://guix.gnu.org/ uses with great success, the Guile Scheme dialect of LISP, to be precise. And FYI the "framework" is:
$ ls --human-readable --size $(readlink $(which guile))
16K /gnu/store/1gd9nsy4cps8fnrd1avkc9l01l7ywiai-guile-3.0.9/bin/guile
Yes, only sixteen kilos, not gigas.
- iso8859-1 3y agoGuix/Nix can use dynamic linking without risk since they know the exact dependency closure. It's not fair to compare a statically linked executable to a dynamic one.
- panzi 3y agoRight, so its still just about 9 MB: guile=$(readlink -f $(which guile)) sizes=$({ echo $guile; ldd $guile|grep /|sed 's+^[^/]*\(/[^ ]*\).*+\1+'; }|xargs -n 1 readlink -f|xargs du -ab|cut -f 1) sumsize=0 for size in $sizes; do sumsize=$((sumsize+size)); done echo $sumsize Gives 9041632 here.
- Bost 3y agoThanks for the snippet. Now I have a recipe how to calculate the size of a binary file, plus the shared objects, i.e. the so-file(s), it requires directly. Now I just need to extend your snippet so that it works recursively. A shared object can require other shared objects.