On Tue, 3 Nov 2015, Nathan Cutler wrote: > IMHO the first step should be to get rid of the evil submodule. Arguably > the most direct path leading to this goal is to simply package up the > downstream civetweb (i.e. 1.6 plus all the downstream patches) for all > the supported distros. The resulting package would be Ceph-specific, > obviously, so it could be called "civetweb-ceph". > > Like Ken says, the upstreaming effort can continue in parallel. I'm not sure I agree. As long as everything is not upstream and we are running a fork, what is the value of having it in a separate package? That just means all of the effort of managing the package dependency and making sure it is in all of the appropriate distros (and similar pain for those building manually) without any of the benefits (upstream bug fixes, etc.). 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
