> On Tue, Feb 21, 2012 at 12:39 AM, David Sommerseth > <openvpn.l...@topphemmelig.net> wrote: >> But remember that all your patches *will* go through review as for >> everyone else in the community. That means either *1)* patch reviews on >> the mailing list, or *2)* reviewed through a sprint review in a >> developers meeting on the IRC. You are free to choose between which >> approach fits you best. But I will not accept patches into the tree >> unless it has been clearly ACKed publicly. > David, > > I see I wasted three days of work. > > You agreed that you have a problem "Huston we have a problem, the > build process of OpenVPN causes maintenance overhead". > > Nobody in this community maintains the build system so it became so > complex and none intuitive that it is unusable. Agreed. I would very much like to see what the alternative is. I'm not interested in details, but the whole. The goal is to have a buildsystem that sucks less. > > You won't be able to review all my changes as it is a revolution not > evolution, I warned you guys ahead! It will touch almost all the > sources. I don't think reviewing individual patches is very productive at this point. It makes perfect sense for incremental, small changes that we want to go to the repository right away. In this case I'd prefer to see a working prototype of the new buildsystem and review it as whole. If it fulfils the basic requirements[1] then we can comment on the details. And then we can start moving the code to the official repository - no need to do it right now.
Could you (the other devs) take a look at Alon's Git tree as a whole and see what you think, without getting into details? I can take a look to see how the MSVC build (w.o. the TAP-driver build) would integrate with it. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock [1] We have not clearly specified these, and we should a.s.a.p.
