[Mono-devel-list] Tarball packaging of Mono.

[Ben Maurer]

>> Probably as a top-level subdirectory.  For development, this can be
>> easily achieved with CVS modules file -- so the eventual distributed
>> directory tree should probably look like that too.
>>
>
> Please no. The mcs and mono modules are already too large. turning them
> basically into one giant module would be painfully insane.

How does this become painful? You are going to need both modules anyways.
What difference is it if they are both checked out into mono/ or if you
have mono/ and mcs/ on the same level?

The only problem I would see with doing this is that all of us who have
gotten used to typing $ROOT/mono/mono/metadata or $ROOT/mcs/class/corlib
would have our paths changed under us. But, am sure we can adapt ;-).