On Oct 8, 2012, at 12:11 , Marcel Moolenaar <mar...@xcllnt.net> wrote:
> > On Oct 4, 2012, at 9:42 AM, Garrett Cooper <yaneg...@gmail.com> wrote: >>>> Both parties (Isilon/Juniper) are converging on the ATF porting work >>>> that Giorgos/myself have done after talking at the FreeBSD Foundation >>>> meet-n-greet. I have contributed all of the patches that I have other >>>> to marcel for feedback. >>> >>> This is very non-obvious to the public at large (e.g. there was no public >>> response to one group's inquiry about the second ATF import for example). >>> Also, given that you had no idea that sgf@ and obrien@ were working on >>> importing NetBSD's bmake as a prerequisite for ATF, it seems that whatever >>> discussions were held were not very detailed at best. I think it would be >>> good to have the various folks working on ATF to at least summarize the >>> current state of things and sketch out some sort of plan or roadmap for >>> future >>> work in a public forum (such as atf@, though a summary mail would be quite >>> appropriate for arch@). >> >> I'm in part to blame for this. There was some discussion -- but not at >> length; unfortunately no one from Juniper was present at the meet and >> greet; the information I got was second hand; I didn't follow up to >> figure out the exact details / clarify what I had in mind with the >> appropriate parties. > > Hang on. I want in on the blame part! :-) > > Seriously: no-one is really to blame as far as I can see. We just had > two independent efforts (ATF & bmake) and there was no indication that > one would be greatly benefitted from the other. At least not to the > point of creating a dependency. > > I just committed the bmake bits. It not only adds bmake to the build, > but also includes the changes necessary to use bmake. > > With that in place it's easier to decide whether we want the dependency > or not. > > Before we can switch permanently to bmake, we need to do the following > first: > 1. Request an EXP ports build with bmake as make(1). This should tell > us the "damage" of switching to bmake for ports. > 2. In parallel with 1: build www & docs with bmake and assess the > damage > 3. Fix all the damage > > Then: > > 4. Switch. > > It could be a while (many weeks) before we get to 4, so the question > really is whether the people working on ATF are willing and able to > build and install FreeBSD using WITH_BMAKE? > I think that's a small price to pay for getting going with the ATF stuff now rather than in 4 weeks. What's the right way to do this now with HEAD? Best, George _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
