On Nov 29, 2011, at 1:46 PM, Esteban Lorenzano wrote:

Hi,

Currently, we are linking official VMs for pharo taking directly from Jenkins a version and packaging for download (or for Pharo One-Click). I think this is a temporal solution, we need something better:

1) Pharo VMs should have Pharo Icons. 2) Pharo VMs should be named "pharo" or "pharovm" (better the fist), not "CogVM", which is an internal name. 3) We should include a PLUGINS.txt file with information about present plugins (internal and external) 4) We should include a LICENCE.txt file with all licence information.

... I think that's all :)

I know... this is very dumb and clearly not mandatory, but it says a lot about the maturity of our Pharo :)

All agree? Should I create a ticket?

yes.

pd: I'm the only one who does not likes One-Click versions? I would prefer a different package for each platform (Is ugly to have a directory named Pharo.app in linux or windows. Also, no need to have all those duplicated-but-for-different-platform files)

Yes, I was thinking about that, too... its nice for the very first step, but then it's more a problem. Maybe having 3 packages for the three architectures would be better? -- Marcus Denker -- http://marcusdenker.de