[Vm-dev] Esteban's workflow for pharo packages in pharo-vm

[bdurin]

I agree, having everything in the same place, even everything on github
maybe, would be very useful!
Sorry, I was not clear, I was refering to more "stupid" things.
In mc, you updated VMMaker to VMMaker.oscog-eem.2243 and Cog to Cog-tpr.325
for example. I guess you choose the versions of the package that you deem
stable or that suit your testing needs. Then, how to you proceed? Have you
got an automated process that retrieve the .mcz from Squeak repo, process it
into all the files that you commit to the git repo? Or do you manually load
the version you want in an image and somehow export the .mcz package that is
in your local package cache into the tree of dir and files that is in the
git repo?
Maybe I can rephrase my question as: how is the set of files that are in
"mc" produced? (All the .package dir, .class dir, .json files, etc.) Is it a
tool that you wrote or is it the output of something "standard" (let's say
that "standard" mean something already in the Pharo image that one can
download from pharo.org)? It seems that I miss something very simple here.
Thanks for your help!
Bruno



--
View this message in context: http://forum.world.st/Esteban-s-workflow-for-pharo-packages-in-pharo-vm-tp4960115p4960381.html
Sent from the Squeak VM mailing list archive at Nabble.com.