Hi! "Antoine R. Dumont (@ardumont)" <ardum...@softwareheritage.org> skribis:
> |-----------+-------------+----------+----------| > | Iteration | Host System | Time (s) | Packages | > |-----------+-------------+----------+----------| > | 1st | Debian | 121.88 | 284 | > | | Guix System | 413.55 | 749 | > |-----------+-------------+----------+----------| > | 2nd | Debian | 1.3 | 101 | > | | Guix System | 11.54 | 354 | > |-----------+-------------+----------+----------| Ah, that’s a significant difference. I guess we can keep both methods: the exhaustive one that goes over all packages, and the quick one. Then we can have a switch to select the method. Typically, we may want to use the expensive one on the build farm to publish a full database, while on user’s machines we may want to default to the cheaper one. >> Oh, and progress bars too. > > I'm a bit unsettled on this. Hopefully it was mostly a joke ;) It wasn’t. :-) In the manifest case, we get ‘all-profiles’ is almost instantaneous, so we immediately known the number of manifests we’ll be working on. In the package case, the number of packages is known ahead. The (guix progress) module provides helpers. But anyway, that’s more like icing on the cake, we can leave that for later. Thanks, Ludo’.
