Adar Dembo has posted comments on this change. ( http://gerrit.cloudera.org:8080/12350 )
Change subject: KUDU-2411: linux: Ship the sasl2 modules with the binary artifact ...................................................................... Patch Set 1: (1 comment) http://gerrit.cloudera.org:8080/#/c/12350/1//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/12350/1//COMMIT_MSG@9 PS1, Line 9: Because different Linux distributions put the dynamically-loaded : libsasl2 modules into different locations, we ship the libraries with : the binary artifact so that we can set SASL_PATH to a known good : location for them at runtime. What happens if we didn't do this? I'm perplexed because the libsasl2 modules are supposed to be something of an implementation detail, found and loaded via libsasl2 itself. What's the failure mode? Maybe you can add the error to the commit message too? -- To view, visit http://gerrit.cloudera.org:8080/12350 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I44afa05bcfa1a29a90f58c72ed6b0752014a16eb Gerrit-Change-Number: 12350 Gerrit-PatchSet: 1 Gerrit-Owner: Mike Percy <[email protected]> Gerrit-Reviewer: Adar Dembo <[email protected]> Gerrit-Reviewer: Brian McDevitt <[email protected]> Gerrit-Reviewer: Grant Henke <[email protected]> Gerrit-Reviewer: Kudu Jenkins (120) Gerrit-Reviewer: Mike Percy <[email protected]> Gerrit-Reviewer: Todd Lipcon <[email protected]> Gerrit-Comment-Date: Tue, 05 Feb 2019 00:36:04 +0000 Gerrit-HasComments: Yes
