contrasting elfutils debuginfod and clr-debug-info server

["Frank Ch. Eigler" <fche@redhat.com>]

Hi -

Through some comments on phoronix [0], just became (re?)aware of the
neat clear-linux debuginfo server facility [1].  It's similar to the
nixos one we have mentioned before in that it relies on a local fuse
server expose remote debuginfo artifacts under /usr/src,
/usr/lib/debug etc.  to local tools.  The server side relies on a web
server [2] that has a carefully unpacked, unified-namespace tree of
all the artifacts into individual .tar files.  This has some
pros/cons, naturally.

Some contrasts in a tabular form:

                    clear-linux                                elfutils

indexed             by filename                                by buildid
client side sw      fuse server                                apprx. none
server side sw      plain file server                          debuginfod
server side disk    unpacked, unified-namespace layout         orig pkg set
multi-version       maybe, if /usr/src/XXXX filenames unique   no problem
multi-arch          req. separate servers                      no problem
multi-distro        req. separate servers                      one server ok

Neat system.  I wonder how interoperation would work.
(cc:'ing a few clearlinux folks just for their information.)


[0] https://www.phoronix.com/scan.php?page=news_item&px=Red-Hat-FOSDEM-debuginfod
[1] https://docs.01.org/clearlinux/latest/guides/clear/debug.html
[2] https://download.clearlinux.org/debuginfo/

- FChE