guyuqi commented on pull request #620: URL: https://github.com/apache/bigtop/pull/620#issuecomment-630050780
>> What's the different between ruby-installation into Bigtop_toolchain and install ruby in the phase of build do-component-build? Isn't both of them lead to the same result? 1. Install ruby-2.4.0 in Bigtop_toolchain: Bigtop_toolchain is the common facility for all components in Bigtop. It would override the ruby package already installed by distros. If put ruby-2.4.0 in Bigtop_toolchain, ruby-2.4.0 is used for both build-time and runtime. Maybe there are some dependency issues for other components which is concened from cos ([comments](https://issues.apache.org/jira/browse/BIGTOP-3346?focusedCommentId=17093457&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17093457)). 2. Install ruby-2.4.0 in do-component-build: It's just for logstash build-time. For logstash runtime, we could leverage the ruby (2.4+ ) provided by distros. 3. Why do we not leverage the ruby provided by distro but install ruby-2.4.0 in do-component-build to build logstash? When `rake bootstrap` in the phase of build, some dependency packages like `minitar-0.5.4` would not be installed properly by leveraged ruby 2.4+ (2.4.10 or 2.5.8) on Arm64 (the problems of `gem `ecosystem on Arm64). For runtime, logstash would work properly on every version of ruby 2.4.0+. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
