I think that the tree reshuffle should be done separately from the cmake branch. I also agree with Ged that it isn't very logical, so from this point of view I support the tree restructure.
On the other hand ReactOS is in a really bad shape form a user point of view and all the resources should focus on fix the most important bugs and regressions listed in http://www.reactos.org/wiki/Buglist. The rest of the things
is of a minor importance to me. We can't do everything at the same time, we should focus and things of major importance at the moment.
Just my 2 cents.

Gabriel.


To: ros-dev@reactos.org; gedmurphy@gmail.com
Date: Fri, 30 Jul 2010 21:05:10 +1000
From: geekdundee@gmail.com
Subject: Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

I might be a bit of a n00b but at this stage, I also support this restructuring of the tree. I also see a potential for optimizing builds to allow for building a set of components, as opposed to having to work out what components go with what and build them all individually.

Might also help as there are loads of branches in the repository, many  that haven't been updated in years, that can be easily reduced in size and/or merged as a result of the scheme.

That's just my thoughts on it, but I'm not really had more than about 3-4+ months experience with the ReactOS codebase.

On Mon, 26 Jul 2010 04:46:07 +1000, Ged Murphy <gedmurphy@gmail.com> wrote:

The logical layout is exactly what is wrong with the tree. The tree is currently laid out in a manner which you would expect someone who doesn't understand NT architecture. Things are laid out by type instead of by architecture.
It makes building individual areas of the operating system very difficult.

On 25 July 2010 19:03, Aleksey Bragin <aleksey@reactos.org> wrote:
Yes, there is no sense in doing two mainly unrelated very big tasks simulteneously. Also my own opinion still hasn't changed - existing layout is quite logical (there are exceptions, but they are everywhere), and any modularization could be achieved already with existing tools like sysgen.
 
Let cmake branch be actual cmake experiment, not an awesome attempt to fix whole ReactOS at once Улыбка смайлик
 
WBR,
Aleksey Bragin.
 

Sent: Sunday, July 25, 2010 9:45 PM
Subject: Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

I also support a reshuffling of the directories, but not in the cmake branch.  Let that be used JUST for getting cmake up and running and if/once that is merged into trunk, then we look into changing the structure.  Best not to complicate one task by adding more to it.


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev




--
Give a man a fish and he will eat for a day.
Teach a man to fish and he will eat for a lifetime.
Give a man religion and he will die praying for a fish.


Non sei a casa? Accedi a Messenger dal Web.