<p>There are people who like to see graphs which are going up over time... for marketing</p><p>Now, on the flipside increasing the package database means that all clients have to do a lot of work: downloading the package metadata, reading the files, the solver working on them, CI systems building documentation, other CI systems trying to build reverse dependencies on new releases.</p><p>Gladly <a href="https://mastodon.social/tags/OCaml" class="mention hashtag" rel="tag">#<span>OCaml</span></a> agreed on a policy <a href="https://discuss.ocaml.org/t/proposed-package-archiving-policy-for-the-opam-repository/15713" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">discuss.ocaml.org/t/proposed-p</span><span class="invisible">ackage-archiving-policy-for-the-opam-repository/15713</span></a> and soon we'll get rid of >10% of packages <a href="https://github.com/ocaml/opam-repository-archive/pull/3" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/ocaml/opam-reposito</span><span class="invisible">ry-archive/pull/3</span></a></p>
