|
From: Casper H. <ch...@us...> - 2002-06-01 00:36:53
|
l=F8r, 2002-06-01 kl. 00:55 skrev KJK::Hyperion: > At 00.16 01/06/2002, you wrote: > >On Fri, May 31, 2002 at 02:49:05PM +0200, Casper Hornstrup wrote: > > > Maybe you don't like it because you still see user32.dll and gdi32.dl= l > > > as Win32 components. Well that all changed when we decided to make th= em > > > native. > >[...] > >I did not realise we had decided this! >=20 > "we" didn't decide, Casper did. The others accepted for lack of better=20 > ideas, or they just don't seem to follow the discussions anymore. Speakin= g=20 > of myself, despite I really care for ReactOS, I chose not to comment=20 > anymore on the topic. I'm losing interest in this sort of things Maybe it was a mistake to assume that this discussion was over, but there has not been any messages in the thread "Fwd: Reorganizing the cvs repository before starting reactos.org" where someone argued against this for two weeks. I would have provided some links to the list archieve, but the sourceforge list archieve is screwed up. I initally wanted to seperate subsystems to their own CVS modules and have subsystems not depend on each other (ie. put the Win32 subsystem in it's own module too just like all other subsystems). David then said that Win32 was inseperable from the ReactOS kernel and that the Win32 subsystem should stay in the reactos module. I did not like the idea of having modules marked win32 only in the required reactos module, so I suggested that we make these "inseperable" Win32 modules native so they don't belong to a specific subsystem and can thus optionally be used in any subsystem that needs the functionality they provide. Then I was okay with putting them in the reactos module. David agreed to this compomize and nobody else has argued against this for about two weeks now. So please present your arguments if you have some; so we can take vote or something. - Casper |