Yes, I also had similar issues with trying to learn reposurgeon.
In the end it was "easier" (perhaps not faster, but less headaches) to use git commands and lots of google/StackOverflow searching.
What I did take from reading up on reposurgeon is that it's a good idea to iterate on a solution:
Set of scripts checked into a seperate git repository.
The scripts start with the source unmerged git repositories and nothing else.
The scripts never modify the source umerged git repositories.
The scripts product is a merged git repository.
I ended up iterating on a Makefile which contained various git commands to take the source repositories (I think there were 13?).
At each step I added more git commands to filter commits, add branches and tags, add commit messages to map original commits to new commits, etc.
Once I was fairly happy with the result, I started trying to use the merged repo, found a few mistakes and had to rebuild it from scratch again, and keep iterating.
Took under a week to do, and theoretically I could run that script again at any time (with possible fixes) to produce an alternative branch, if I ever find issues.
It's indeed a shame that reposurgeon is super-niche. I suspect that's why the author charges consultancy fees (which is fair enough).
Grew up in Russia, lived in the States, moved to Germany, sometimes live in Spain. I program since I was 13. I used to program games, maps and now I reverse engineer password managers and other stuff
Location
Berlin and Málaga
Education
MS in CS from State Polytechnic University of St. Petersburg
Yes, I also had similar issues with trying to learn reposurgeon.
In the end it was "easier" (perhaps not faster, but less headaches) to use git commands and lots of google/StackOverflow searching.
What I did take from reading up on reposurgeon is that it's a good idea to iterate on a solution:
I ended up iterating on a Makefile which contained various git commands to take the source repositories (I think there were 13?).
At each step I added more git commands to filter commits, add branches and tags, add commit messages to map original commits to new commits, etc.
Once I was fairly happy with the result, I started trying to use the merged repo, found a few mistakes and had to rebuild it from scratch again, and keep iterating.
Took under a week to do, and theoretically I could run that script again at any time (with possible fixes) to produce an alternative branch, if I ever find issues.
It's indeed a shame that reposurgeon is super-niche. I suspect that's why the author charges consultancy fees (which is fair enough).
Yeah, I also iterate on scripts and use
gitto keep track of progress. I don't domkdir ...anymore for new projects, I just saygit init ....