Hi, I documented Snapshotcello here: http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-ready http://www.tudorgirba.com/blog/snappier-snapshotcello
In short, the reason for Snapshotcello is to deal with deeply nested configurations, like we have in Moose, in a reliable way. So, the goal is to be able to develop on the latest package version at all time, and when ready to take a reloadable snapshot. For now, this implies flattening everything. The actual version strings are not written in the version method because of the 256 literals limitation. So, we are writing all version strings in an array, and creating a Metacello version out of them. In any case, if you want to create a proper Metacello version, all you have to do is: - load the snapshot version - then create a version based on the corresponding baseline (usually the last baseline) - publish the configuration Doru On Sun, Nov 10, 2013 at 10:26 AM, Norbert Hartl <norb...@hartl.name> wrote: > > > Am 09.11.2013 um 22:04 schrieb Tudor Girba <tu...@tudorgirba.com>: > > There is a very easy way. Create a configuration version that explicitly > specify the package versions without Snapshotcello. > > There is still version 1.6 that is made that way. I tried using it with > Versionner but that doesn't work. I load 1.6 but the next time I create a > new version it assumes I have 1.8-snapshot loaded which I cannot load > afterwards because I refer only to the core but the group isn't there. So > even if I would add a manual version I assume it will break the next time > you guys add one. > Btw. is the metacello mangeling part in Snapshotocello und Versionner not > something where forces should be joined? Versionner generates versions that > have the individual package versions written in the method. > And I have no glue why snapshotocello is not writing the versions in the > version method. My gut feeling is that metacello is complex enough and > putting another layer of dynamism in the mix that tries to be clever is > probably not the best choice. > > Norbert > > Doru > > > On Sat, Nov 9, 2013 at 3:38 PM, Norbert Hartl <norb...@hartl.name> wrote: > >> >> >> Am 09.11.2013 um 12:21 schrieb Stéphane Ducasse < >> stephane.duca...@inria.fr>: >> >> Indeed. >> I see >> and I did not got the time to fix the issue I saw when applying on >> private projects. >> >> Agreed. But, the ConfigurationOfPetitParser is up to date. It has groups >> to distinguish between between core and gui. >> >> The only problem that Norbert raised is that when using Snapshotcello, >> the groups are lost due to flattening of the entire configuration. >> >> Which makes it unusable for me. Or at least I didn't figure out a way how >> to circumvent this behaviour. >> >> Norbert >> >> Doru >> >> >> On Sat, Nov 9, 2013 at 2:12 AM, Stéphane Ducasse < >> stephane.duca...@inria.fr> wrote: >> >>> Guys >>> >>> even if one day we may integrate petitparser (so far I do not see why - >>> but do not comment). We need an up to date configuration >>> because we want everything with configuration because we want to >>> bootstrap 4.0. >>> >>> Stef >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > -- www.tudorgirba.com "Every thing has its own flow"
