On Thu, Sep 29, 2016 at 12:00 PM, Sage Weil <sweil@xxxxxxxxxx> wrote: > Hi everyone, > > Matt has a working boost submodule branch ready; I've pushed it to > wip-boost in ceph.git to ensure the gitbuilders are happy and tagged it > needs-qa. > > Just so there are no surprises: > > * This change increases the initial checkout + clone time by about > **three minutes**. Boost is structured as several dozen submodules and it > takes a while to clone them all. It's painful on the first checkout, but > fine after that. This pain only applies to developers. > > * We are using boost 1.61 + a few things. There are still some > outstanding warnings. They appear to be issues in boost 1.61 itself, and > do not appear to be significant. (And the warnings are in parts of boost > we're not using yet: asio and serialization.) > > * There is still the option to use a system boost via a cmake option. I > doubt anyone will opt for this in practice given the distros tend to lag, > but they can if they want. What does this mean for actual builds/releases? It seems there is a potential for a disconnect between what a developer expects from the submodule vs. what the distribution may provide. Or are builds supposed to embed boost and not use the distro-provided version? > > sage > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
