Rectify / Modify change

[stschiff]

We will remake the current rectify. This whole process was started in a now closed PR #337 which ended with this final discussion point by @nevrome

Stephan and I had another discussion about this. Here's a quick summary of my understanding of the results:

The old, non-smart rectify was useful and should be preserved as is. It should get a new name (e.g. modify/alter/manipulate). Its flaw of editing every package below the base directory should be documented clearly. We could consider extra measures like a warning when editing multiple packages, or even a flag that has to be set in case multiple packages will be affected.
A new, smart subcommand rectify should be added. It automatically adds and corrects checksums and bumps the version of packages whose checksums have changed. It has only four options: -d (naturally), --packageVersion VPART and --logText STRING (mandatory), and --newContributors DSL (optional).

[nevrome]

Looking at this again I think the new rectify should still allow to adjust checksums without incrementing the version number. Maybe we could make --packageVersion VPART and --logText optional (though if one is there, the other must be as well).

A good example where this is relevant is this commit here: poseidon-framework/community-archive@a72f6c5 The package author just wanted to change a technical detail of the .janno file in a draft package, which does not warrant a change in the version number. This common case should ideally be handled with a simple call to trident rectify -d ., right?

[stschiff]

Yes, that makes sense!