Aleksey Bragin wrote:
We have chatted with Art a bit on this topic
yesterday, and our
opinion seems to be that trunk/reactos should include all stuff
included in a default Windows
I'm pretty sure, such a rule will sooner or later lead to questions like "I
don't need this app for my testing, so why was it included?" (for example,
if we would add the mspaint clone from forum user gyROS)
Furthermore, there could also be useful stuff from our side, which should
have a right to live in "reactos". This shouldn't be limited to the
components Windows provides.
One of the other suggestions I remember was something like making "reactos"
contain only the very basic stuff to keep compilation times low.
but with a modification to rbuild to
allow tags for each module, and later build by tags.
Please explain this in more details.
A concept called "buildfamilies" was already implemented in the rbuild
branch, but nothing of that stuff was backported so far.
I'm also concerned that we don't have a clear plan on how to proceed with
our buggy rbuild now.. (at least from what I got to know)
Or should we have a voting?
Probably better to finally have an agreement between all devs.
Best regards,
Colin