[Vm-dev] a Cog branch

[Geoffroy Couprie]

On Fri, Jun 25, 2010 at 10:09 AM, Andreas Raab <andreas.raab at gmx.de> wrote:
>
> On 6/25/2010 1:05 AM, Geoffroy Couprie wrote:
>>
>> On Fri, Jun 25, 2010 at 9:53 AM, Andreas Raab<andreas.raab at gmx.de>  wrote:
>>>
>>> On 6/24/2010 7:16 PM, Igor Stasenko wrote:
>>>>
>>>> One user could create a project, then others may create forks or
>>>> subforks of his project(s)
>>>
>>> How exactly is this a good thing? I don't want 200 forked Squeak VM
>>> versions; I want one canonical source that people can build from.
>>>
>>
>> Forks can be really useful for people who have to maintain a set of
>> patches that may not be accepted in the repository (applications
>> requiring a specific VM configuration, servers, etc).
>
> Do we have this problem? What patches do you or anyone else have that can or
> should not be integrated in the main source?
>

I have my CMake patches (to be able to build the Windows VM with
CMake), and some patches to build the Windows VM with GCC. I sent the
patches here 2 months ago (you never answered on that thread), and
although people seemed interested by that code, it was never added in
the repository. I had to store the CMake patches, and then the other
Windows patches, and working on these different pieces of code without
being able to commit was painful.

I also modify the VM for self education/fun purposes, and these
modifications would never be accepted in the main tree (heavily
breaking large parts of the memory allocations, weird plugins, etc).