Sakamoto Noriaki

This will mitigate this situation: - backward-incompatible enumitem is released: - some libraries use enumitem to verify their packages; thus they should be removed from the snapshots. https://github.com/na4zagin3/satyrographos-repo/pull/412

@zeptometer It's caused by a dependency problem where ancient versions of Satyrographos which don't compile with core v0.14. The [versions hosted in the official OPAM repo](https://github.com/ocaml/opam-repository/blob/67747ba143c27b8874bb3bb88474a470058363f4/packages/satyrographos/satyrographos.0.0.1.4/opam) have been fixed. I'll...

New package schema #24 can allow automatic install.

It’d better to abstract the underlining package manager as a _resolver_ as `install -resolver opam -package zrbase` installing zrbase from OPAM repository.

Satyrographos needs to run unit tests like https://github.com/nyuichi/satysfi-base/pull/15

We can switch the feature to keep backward compatibility. - satyrographos 0.0.1 series keep the behavior - satyrographos 0.0.2 series provide the new schema by default Regardless of series, automatic...

We need to rethink about semvar. Allowing multiple versions of a library can break type safety.

Local package installation is in fact useful for usual documents as requested in https://github.com/gfngfn/SATySFi/issues/154.

`-C` option has been introduced by https://github.com/gfngfn/SATySFi/pull/161. We may have to avoid using that in order to support 0.0.3 and older SATySFi versions.

`-C` option simply adds specified directories to the search path. For clean build, we need to clear out the default search path. It’d better to submit a MR to add...