Planning

[bvssvni]

The major usage of this tool will be to check if libraries are updated and what versions they should have when some of the dependencies have a breaking change.

An idea is to use piston_meta to decouple some steps, such that the data can be generated and tested in various ways:

• A custom format for extract info (libraries to extract information from)
• An algorithm for extracting information and generating data for versions and dependencies
• A custom format for dependency info (describes all we need to know about the ecosystem)
• An algorithm for generating update info
• A custom format for update info (libraries that need to be updated and new version number)

There are 3 different custom formats:

1. extract_info which tells where to get dependency_info
2. dependency_info contains all information required to reason about the ecosystem
3. update_info contains actions that needs to be done

extract_info_from(extract_info) -> dependency_info
update_info_from(dependency_info) -> update_info

[bvssvni]

Done.