Kaelyn <[email protected]> writes: > Hi, > > On Wednesday, December 10th, 2025 at 11:21 AM, Tomas Volf <[email protected]> > wrote: > >> >> >> Cayetano Santos [email protected] writes: >> >> > This is why I’m thinking a bout something as simple as: >> > >> > guix build qucs-s >> > /gnu/store/lfg34wzx83mjla81kh38yjpx0r7xq43i-qucs-s-25.2.0 total : 2749.2 >> > Mio >> >> >> Please no. It would break usage of guix build in scripting. I have few >> scripts where I am doing stuff like jq=$(guix build jq)/bin/jq ... > > That is a valid concern. I think the way to handle adding the extra > information would be to print it out on stderr just like the rest of > the build output.
Well, that would be one way, but could lead to fun output like this:
$ pkgs=$(guix build qucs-s gucs-z)
total : 2749.2 Mio
total : 1749.2 Mio
Which I would argue is not very useful. ^_^ You could figure out some
heuristics, but them being heuristics, they would fail some of the time.
So I really think your second suggestion (guix lint) is the place to put
this into (if somewhere).
But some service tracking this data over longer time and presenting some
trends for package would likely be better.
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
