Well, it for sure looks interesting. Once one has the understanding about configurations. Which will lead to look for something like that tool.
Not sure I am mastering configuration basics at the moment... So, that's why I guess. Phil 2013/4/11 Norbert Hartl <norb...@hartl.name> > Huh, I find it strange that nobody cares. Does anybody use Versionner? > > Norbert > > > Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norb...@hartl.name>: > > Yesterday I tried again to use Versionner in 2.0 but did have much > success. So I tried myself (because I think Versionner is important) and > could final generate a new version of my project using versionner. > > Following things I noticed (I'm writing this because I'm not sure which > issue to open for what package. I'm just want opinions and after that I can > open/upload whatever): > > I loaded Versionner from Metacello (taken from [1]) > > Gofer new > url: 'http://ss3.gemstone.com/ss/Versionner'; > package: 'ConfigurationOfVersionner'; > load. > (Smalltalk at: #ConfigurationOfVersionner) perform: #load > > monticello issues > ============= > > While updating the rest of the packages to the newest I saw that > > Versionner-Core-Model-ChristopheDemarey.19 > > has an older ancestor for fixing something for pharo 1.4. The package > > Versionner-Core-Model-ChristopheDemarey.20 > > merged the packages back to HEAD but reverted some things like > SystemAnnouncer back to SystemChangeNotifier. So I'm using > > Versionner-Core-Model-ChristopheDemarey.18 > and > Versionner-Core-Commands-ChristopheDemarey.17 > > as older packages. Any other package is the newest in the repository. > > metacello toolbox issues > ================== > > I don't know much about metacello toolbox but the separation of files into > ConfigurationOf and Baseline seems to have potential for confusion. There > is a notion of a basename so it can build ConfigurationOfMyProject as well > as BaselineOfMyProject (MyProject being the basename). But in the > MetacelloToolbox in the pharo2.0 repository it does not seem right. I had > to change the code to use (MBToolbox baseNameOf: …) at a few places. I took > orientation from the message signature. If a method expects a > configurationBaseName and the sender used the configuration class I changed > it. I'll attach the mcz for now to this mail until it is clear what to do. > > versionner issues > ============= > > At one place I added a metacello toolbox name conversion because it made > sense to make it there. The other thing I had to fix is a method > notification that takes the wrong entity from an announcement. Both > packages attached as I don't have commit rights and don't know where the > issue tracker for versionner is if there is any) > > I would be glad if any of you guys that know about that stuff could drop > me a note if this is ok or where I've gone wrong. > > thanks, > > Norbert > > > [1] http://users.dcc.uchile.cl/~jsandova/versionner/ > > <Metacello-ToolBox-NorbertHartl.136.mcz> > <Versionner-Core-Commands-NorbertHartl.18.mcz> > <Versionner-Core-Model-NorbertHartl.19.mcz> > > >