Hi, On Mon, 02 Dec 2024 at 14:44, Ludovic Courtès <l...@gnu.org> wrote:
> This manifest is just an example. We could come up with manifests > targeting package collections like CRAN packages, astronomy packages, > and so on. Let consider that a “leaf” package is a package that does not appear elsewhere in any other packages. Then, if there is no mistake, I count 14143 leaf packages over 32459 all packages. Well, if we filter using gnu-build-system and cmake-build-system then it reduces to 2847 packages. These packages are “safe” to automatically update because the only annoyance will be users at run time. ;-) Somehow, the loop and type conversion are not optimized but maybe this kind of “leaf” packages could defined and then filtered build-system per build-system, i.e., team per team. WDYT? Cheers, simon
