Le lundi 04 avril 2016 à 08:54 -0400, Jeff Darcy a écrit : > > Once this was done, I pushed to use the regular upstream change, > > something that was not done before since the local change broke > > automation to deploy test suite on Freebsd. > > It looks like we have two options here: > > (1) Fix configure so that it accurately detects whether the > system can/should build BD, and stop forcing it on the command > line. > > (2) Leave it on the command line, but add a platform check to > determine its proper value. > > There's already a platform check in Prasanna's patch to set > the parallelism level. Should we just combine that with #2? So from a end-user (read packager) perspective, we should strive at: 1) detect when people push unsupported option as soon as possible (ie, if BD is not compiling or working on freebsd, detect in the configure, not at build time) 2) enable features by default that we think to be beneficial, on platform where they are supported. In fact, i would go as far as enabling all by default, so we can get a wide testing from the smoke test. Or optionally, having a --enable-all-supported would permit to have supported options in sync with the code. If someone add support to BD to freebsd in some version, we wouldn't have to make anything special on the slave to build the option on one branch and not the others. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
