Hi guys, Let's say there is a project which is being build with metadata-less GitFileTree. There is a BaselineOf and a ConfigurationOf which work correctly. And ConfigurationOf can perfectly have fixed "versions" that could be, at some point, integrated in Pharo.
Let's say I release version 1.0 which is INTEGRATED inside Pharo. When Pharo image is build, it uses ConfigurationOfMyApp to load the code and so there will be NO history of versions (cypress.1). Now, as Pharo goes on, there may be changes to that project as part of refactors or whatever that happens in-image. So in one months from now, Pharo may have a "newer" code than the originally released 1.0. Let's say that for the package MyAppPackage were only 3 commits in those 2 months. At the same time, I have continue working with my project, and I am ready to publish 1.1. Question is.... how do I bring Pharo changes to my own place? 1) Fetching (from Pharo repo) and pushing to my GitFileTree only the versions during those 2 months? I doubt this will work as crappy Monticello numbers could have collisions, right? 2) Doing a poor man diff and cherry picking changes from Pharo repo and manually apply them to my own repo? In this case, the "3 commits" of those 2 months will be lost as from git history version. Is there a project doing this?? I know QualityAssistant is close, but he does not use metadata-less GitFileTree I think...so I am not sure. Thoughts? Thanks! -- Mariano http://marianopeck.wordpress.com
