Casper Hornstrup wrote:
Like in CVS, after the conversion, the other subsystems will get their own Subversion module. Ie.
/trunk/reactos /trunk/os2 /trunk/posix
This require developers of the OS/2 and posix subsystems to check out both the os2/posix and reactos modules, but it makes it possible for the Win32 developers (which are still the majority) to only checkout a single module in order to build a bootable CD. Here, I assume that we can all agree to move freeldr to /trunk/reactos/freeldr after the conversion.
I forgot that: I think it is fine having separate modules for optional subsystems and requiring having the core system too to build them. The problem I spot in the main module is mixing core os and win32 pieces. As I said, there are two ways: a) forget NT and say ROS is a Win32 reimplementation (you don't need separating native and Win32 CSR/GUI modules); b) remember ntos is the system and that it can run *without* Win32, therefore make apparent there are two distinct pieces of software in the 'reactos' module.
Emanuele Aliberti