Hi, Cayetano Santos <[email protected]> skribis:
> 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 > > or > > guix lint qucs-s > ... > total : 2749.2 Mio > > to make this explicit, the previous total being the output of ’guix size’. In theory yes; in practice that needs more thought because computing the closure size is relatively expensive (computing the size of the thing itself comes for free once it’s built). >> Maybe one thing we can do is to organize an on-line hackathon where we’d >> team up to focus specifically on this issue for one or two days? >> There’s already a call for action in >> <https://codeberg.org/guix/guix/issues/938#issuecomment-8593863> that >> could be used as a starting point. > > Why not ? I feel you’re almost volunteering to organize it. :-) > Personally, I’m mostly concerned about a long term, everyday effort > towards reducing the size of packages when possible. Yes, that requires constant attention. There are things we could do to help. Cuirass or the Data Service could keep track of package sizes (in my NixOS days Hydra would do that and could display graphs for individual packages). But in the end, there’s no silver bullet: we all have to pay attention to this and dedicate some of our hack time to trimming extra disk usage. Thanks, Ludo’.
