Esteban's workflow for pharo packages in pharo-vm

 

 

> On 11 Aug 2017, at 17:56, Bruno Durin <[hidden email]> wrote:
>
> Hi Esteban,
>
> In the pharo-project/pharo-vm git repo, what is your workflow to maintain the metacello filetree export in "mc" directory? It seems that you are able to select the version of each package from the standard smalltalk code repositories.

is just a mirror of VMMaker and plugin repositories (I like to have all in one, so I know I can reproduce with just one checkout :P)
but if you develop, your contribution should be on the official repositories…

Esteban

ps: another discussion is my eternal request of putting all plugin sources in a single repository (ideally in VMMaker or in a repository called VMPlugins), but well, it is not the most popular opinion here ;)

>
> Thanks,
> Bruno

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

 

> On 12 Aug 2017, at 10:02, bdurin <[hidden email]> wrote:
>
>
> 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

not really, there is a jenkins job that checks vmmaker repository and moves the package each time.
same should apply to Cog but there are still some merge issues with that package and I’ve been too lazy to do it so I manually make the merge and upload time to time (not very professional :( )

is just “filetree” format, which is already in the image (since a lot).
(is used to export mcz as you see them… used to version them using git/hg/darcs/whatever you want).
it is actually the same format iceberg uses.

cheers,
Esteban

> 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.

Ok, "filetree" was what I missed.
Thanks!
Bruno