You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One bad piece of UX of straight.el currently is that as soon as you hit either a built-in package or a package on EmacsMirror, then straight.el tries to clone EmacsMirror, and this takes forever—even on a fast network connection. I think we can fix this problem.
The easiest way, IMO, would be to extend gnu-elpa-mirror to maintain a mirror of the epkgs repository with the SQLite database file removed. This would effectively solve the problem because the resulting repository would be tiny and fast to clone.
The text was updated successfully, but these errors were encountered:
Since emacsmirror/epkgs@35d6f35 the epkgs repository no longer tracks a sqlite database. Instead of the binary database file epkgs.sqlite it tracks a text file epkgs.sql, from which the former is created on the client-side.
The epkgs repository does not contain any history from before this change. That history is preserved in a separate repository epkgs-v4.
One bad piece of UX of
straight.el
currently is that as soon as you hit either a built-in package or a package on EmacsMirror, thenstraight.el
tries to clone EmacsMirror, and this takes forever—even on a fast network connection. I think we can fix this problem.The easiest way, IMO, would be to extend gnu-elpa-mirror to maintain a mirror of the epkgs repository with the SQLite database file removed. This would effectively solve the problem because the resulting repository would be tiny and fast to clone.
The text was updated successfully, but these errors were encountered: