On Mon, Dec 21, 2015 at 4:31 PM, Bobby Holley <bobbyhol...@gmail.com> wrote:
> I CCed them upthread, but then the subsequent reply dropped them. ;-) > > I would suggest starting a new, explicit thread with a summary of what's > been discussed thus far (rather than asking them to jump into this one), > and CCing dev-servo. > Happy to. > > That being said, my guess is that it's going to be a mostly academic > discussion, because the workflow issues mentioned above would likely lead > us to vendoring even without the requirements from the build peers. > We assume that those workflow issues can be addressed relatively quickly (Q1 2016), so it's more than just academic to me :) Also, I'd like to make Cargo's workflow appropriate for other, similar scenarios, so understanding the constraints more deeply is useful regardless of what Gecko does in the short term. -- Yehuda > > On Mon, Dec 21, 2015 at 4:21 PM, Yehuda Katz <wyc...@gmail.com> wrote: > > > On Mon, Dec 21, 2015 at 4:17 PM, James Graham <ja...@hoppipolla.co.uk> > > wrote: > > > > > > > > It is not immediately apparent to me if that is sufficient to meet the > > > Gecko requirements, but again, having this conversation on a list > without > > > gps, ted, glandium and other build peers seems rather counterproductive > > > since they know both the requirements that we have from our current > build > > > system, and the improvements that are in the pipeline for next year > > (which > > > I understand to be numerous and considered a priority). Without this > > > information it's impossible to tell if any proposed change to cargo is > > > solving the right problem. > > > > > > Can we get them here? I'm very interested in working through this with > > someone who knows all of the constraints deeply. At minimum, I would like > > Cargo to be a suitable tool for people in similar situations as much as > > possible. > > > > -- Yehuda > > > > > > > > > > > > > _______________________________________________ > > > dev-servo mailing list > > > dev-servo@lists.mozilla.org > > > https://lists.mozilla.org/listinfo/dev-servo > > > > > _______________________________________________ > > dev-servo mailing list > > dev-servo@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-servo > > > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
