Hello! Christopher Baines <m...@cbaines.net> skribis:
> I'm not quite sure how that would work, but the Guix Data Service can > query for narinfo files, and from those it can store the size of > specific outputs, as well as there references. > > So the closure size (I think?) is the size of an output, plus the > closure size of all of its references (the definition is recursive). Yes. So the Data Service could pick that info from narinfo files and have per-package pages with a graph showing the closure/self size evolution—IOW, ‘guix size’ over time. Doable, but easier said than done! Ludo’.
