Hi Esteban,<div><br></div><div><br><div class="gmail_quote">2011/11/29 Esteban Lorenzano <span dir="ltr">&lt;<a href="mailto:estebanlm@gmail.com">estebanlm@gmail.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
Currently, we are linking official VMs �for pharo taking directly from Jenkins a version and packaging for download (or for Pharo One-Click).<br>
I think this is a temporal solution, we need something better:<br>
<br>
1) Pharo VMs should have Pharo Icons.<br>
2) Pharo VMs should be named &quot;pharo&quot; or &quot;pharovm&quot; (better the fist), not &quot;CogVM&quot;, which is an internal name.<br>
3) We should include a PLUGINS.txt file with information about present plugins (internal and external)<br>
4) We should include a LICENCE.txt file with all licence information.<br>
<br>
... I think that&#39;s all :)<br>
<br>
I know... this is very dumb and clearly not mandatory, but it says a lot about the maturity of our Pharo :)<br>
<br>
All agree? Should I create a ticket?<br></blockquote><div><br></div><div>I completly agree.</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Cheers,<br>
Esteban<br>
<br>
pd: I&#39;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)<br>
</blockquote><div><br></div><div>I understand but on the other hand it is great to have the same package which contains everything and runs everywhere.</div><div><br></div><div>Luc</div><div>�</div></div><br></div>