<div dir="ltr">One could thing of doing a git submodule with them but it is more trouble than it is worth.<div><br></div><div>I want to be able to clone the VM and compile it right away.</div><div><br></div><div>Phil</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 22, 2016 at 10:11 AM, Norbert Hartl <span dir="ltr"><<a href="mailto:norbert@hartl.name" target="_blank">norbert@hartl.name</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>Am 22.06.2016 um 09:51 schrieb Fabio Niephaus <<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>>:</div><br><div><div dir="ltr">AFAIK the pharo-vm projects generates the sources from the VMMaker package during a build.<div>Wouldn't it be better if the OpenSmalltalk vm does the same? Then no one needs to generate source manually anymore and we don't have millions of lines [2] of generated code in the repository.</div><div><br></div></div></div></blockquote>How would you release a version of the vm? This is only possible of you archive the static artefacts.</div><div><br></div><div>Norbert</div><div><br><blockquote type="cite"><div><div dir="ltr"><div>Fabio<br><div><br></div><div>[1] <a href="https://github.com/pharo-project/pharo-vm" target="_blank">https://github.com/pharo-project/pharo-vm</a></div><div>[2] see Eliot's stats at <a href="https://github.com/OpenSmalltalk/vm/graphs/contributors" target="_blank">https://github.com/OpenSmalltalk/vm/graphs/contributors</a></div><div><br><div>-- <br></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jun 22, 2016 at 4:02 AM David T. Lewis <<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Tue, Jun 21, 2016 at 11:11:28AM -0300, Laura Perez Cerrato wrote:<br>
><br>
> Hi everyone,<br>
><br>
> Excuse me if this has been asked already or it's documented somewhere and I<br>
> missed it, but what's the criteria to update the code in /src, /stacksrc,<br>
> /spursrc and other similar folders in the repository?<br>
><br>
> -Laura Perez Cerrato<br>
<br>
Good question. Traditionally, Eliot generates these sources periodically and<br>
commits them to the repository (and in recent years I have done that chore for<br>
the old trunk interpreter VM). At this point, unless Eliot advises otherwise,<br>
I would suggest that no one other than Eliot should commit to the /src trees.<br>
<br>
Dave<br>
<br>
</blockquote></div></div></div></div>
</div></blockquote></div><br></div><br></blockquote></div><br></div>