+1 for keeping rostests separate
+1 for even more modularity

also i wish we would use/exploit the svn externals feature whenever
possible instead of importing 3rd party code into our repo

On Thu, Mar 8, 2012 at 10:21 AM, Sylvain Petreolle <spetreo...@yahoo.fr> wrote:
> I fully agree with Timo.
> We don't need to have useless files in tree.
> Remember we recently deleted stuff from the main tree for the same reasons :
> space used and download time.
>
> We do need tests, they are critical, but not in every reactos checkout.
> I am for making tests a complete separated project, which would lower build
> times even more.
>
> Kind regards,
> Sylvain Petreolle
>
> ________________________________
> De : Timo Kreuzer <timo.kreu...@web.de>
> À : ReactOS Development List <ros-dev@reactos.org>
> Envoyé le : Jeudi 8 mars 2012 1h27
> Objet : Re: [ros-dev] [ros-diffs] [jgardou] 56082: [DAMN_IT] - addendum to
> r56081
>
> Am I the only one against that?
> Tests are tests, not reactos.
> Why do I need to have another bazillion files in my source tree that I don't
> need or want?
> I have ONE checkout of rostests, but a dozen checkouts of reactos. For amd64
> work I even disabled build of a lot of stuff that was pointless. Now even
> more stuff spread thoughout the whole tree? Possibly even built by default?
> Deleting a full reactos checkout is already slow enough. Also every commit
> to rostetsts is a possible build breaker and can cause massive rebuilds.
> Configure time will also increase.
> I would rather prefer to make it even more modular, instead of mixing stuff
> even more.
>
> -1
>
>
> _______________________________________________
> 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

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

Reply via email to