* Russ Allbery <r...@debian.org>, 2014-08-31, 09:08:
If we want, as a project, to monitor the size of the required,
important, and standard sets, I feel like we should do that directly:
run a cron job somewhere that remembers the previous size, calculates
the new transitive closure, and mails out a report once a week or month
or something listing which packages were added or removed and their
sizes, as well as the total installed size of each of those sets. I
think that would be more effective and more directly on point than
mucking about with trying to monitor priority changes.
Yes, that would be a good idea.
We should probably also monitor package conflicts. We made a big fuss
about node vs nodejs (and rightly so); but I bet that we have lots of
other package pairs in the archive that can't be co-installed for no
good reason.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140904193554.ga3...@jwilk.net
