Hi, On 2020/05/08 08:17, Hans de Graaff wrote: > On Thu, 2020-05-07 at 09:29 +0200, Michał Górny wrote: >> >> 1) list of selected packages (@world) >> >> We would use this to determine the popularity of individual packages, >> plus by scanning their dependencies we would be able to make combined >> statistics for direct usage + dependencies of other selected >> packages. >> This would allow us to judge which packages need more of our >> attention. > At work we install a lot of dependencies through a few company-specific > virtual packages, e.g. company/developer for all stuff useful for our > developers. These packages would then be missed in the statistics. I'm > not sure how prevalent this is and to what extend it wills skew the > statistics.
You raise a valid point. The company/developer package itself I don't think is relevant. The fact that some/package::gentoo is installed as a dependency of company/developer may carry some relevance. So we do need the full list of packages installed, filtered to ::gentoo, but there needs to be an indicated whether it's installed because it's in @world, as a dep of something in @world (which is possibly not in ::gentoo), or is some form of no-longer needed dep. Otherwise I agree with Michał on the four items to be taken. I do still think that the ability to define additional information sets would be useful for building more invasive functionality sets, not necessarily supported by Gentoo. For an organization if they can define a set that grabs a certain amount of hardware details for example that could help with inventory management. Kind Regards, Jaco
