Hi,
after many-o-hours spent on my git-migration tool (
https://github.com/peteruhnak/git-migration ), I've concluded that the
migration cannot be properly done for packages.
In mcz/monticello, every package has an independent history and can change
independently of each other.
In git, this history is merged into a single hierarchy, therefore:
* a specific version of package A mandates specific versions of every
other package in the project
* it is not possible to do a 1:1 migration from mcz to git and keep
this flexibility
Both ways (mcz and git) have advantages and disadvantages of their own, however
as far as I could tell, they are incompatible; so mcz flexibility and some
information (history) will be lost during migration.
The only solution I see is to either separate every package to a separate git
project to keep the flexibility or use git subtree/git module... which are both
complications...
As a git commit specifies the code in the entire project, even across packages,
then I wonder what is the point of expressing package dependencies _within_ the
project (whether in BaselineOf or Cargo).
Peter
