IAHM-COL wrote in Sun Feb 08, 2015 9:49 pm:Notes about FGDATA test with submodulesThe rebasing of all aircraft in FGDATA has not taken place. Thus the FGDATA still points to the history-less initialization commit.
I am unsure how that will work at the moment, and the rewritten history may have broken the FGDATA until all the aircraft submodules are rebased, and point to the latest commit.
Just as I was predicting.
I was rewritting the history of every aircraft, one aircraft at a time, and while doing so, I was bringing back the previous commit history of every of these aircraft!
In my opinion that was a really cool thing to do, as now every aircraft NOT IN BASE is a repo of its own, but also, it has inherited its commits log from the large fgdata hosted in gitorious.
While doing so, I was breaking the FGDATA test1 one aircraft at a time. Why? because this was pointed to a commit for every aircraft that ceased to exist every time I re-updated the aforementioned aircraft. To solve that, I had to generate FGDATA in this case, now with all submodules pointing to the latest dev stage of the aircrafts. And I DID IT NOW
SO
Submodular FGDATA is now ready for early adopters and testersI welcome everyone to test ride this method, try to gather feelings, opinions, and suggestions. Compare this to developing ALL of our aircraft via a centralized SVN server that just a few can SAFELY access.
Remember, some general guidelines of how to test this submodular FGDATA are provided above (and linked below)
viewtopic.php?f=28&t=25314#p231506Also remember, I will be very happy to get the FGDATA commiters to just provide me with a GITHUB account, and I will then grant access to the FGDATA and FGMEMBERS tree.!!
This FGDATA repo is STILL a test versionThe ideal here will be that we have a FGDATA without the aircrafts that is smaller in size but has a preserved history, as well as maintain the branch structure of the current FGDATA. In addition one that the dev-cores in maintaining and developing. Then, from that, I could clone/fork and fetch all upstream changes they make.
Finally, I keep a little light of hope that SVN will be an abandoned idea, or one that is keep cool and calm instead. And maybe everyonce certain time it may be possible to update the modular repo with changes that stubbornly end up in the wrong place (a.k.a SVN fgaddon)
Best,
IHCOL
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it? Probably not, because if they don’t recognise their freedoms, they’ll let their freedoms fall