Hi Joe, my desired chunk size is 500MB. This is a something compromised solution, it may achive the goal to mirror all components, but no help to reducing the whole toolchain's size, and also will bring more complexity to the download logic, which I wonder if it's worth to do. Although, I think it's a down-to-earth solution if more developers need. Currently I soved it by manual reducing the packages's size and repack them, fortunately I only need to handle a small number of packages.
Thanks, Xiang Yang 在 2022-08-05 00:59:22,"Joe McDonnell" <joemcdonn...@cloudera.com> 写道: >We could modify the toolchain to split large files into chunks so that no >chunk exceeds a certain size. Then we could change the downloading logic to >reassemble them. Would that help? If so, what chunk size would work for you? > >Thanks, >Joe > >On Wed, Aug 3, 2022 at 8:26 PM yx91...@126.com <yx91...@126.com> >wrote: > >> Hi Team, >> I'm working on https://issues.apache.org/jira/browse/IMPALA-11454, aim >> at reducing the kudu package's size in toolchain. I found that after >> stripping binaries for kudu release package, we can save 264M in final >> tar.gz file, though we may lost symbols for kudu release package, but I >> think it is acceptable. >> do you agree to strip binaries in toolchain release packages? I would >> like to hear your opinions. >> >> >> >> >> >> >> Thanks, >> Xiang Yang