On Wed, Aug 2, 2017 at 7:39 AM, Alfredo Deza <adeza@xxxxxxxxxx> wrote: > The ceph-debuginfo package has continued to increase in size on almost > every release, reaching 1.5GB for the latest luminous RC (12.1.2). > > To contrast that, the latest ceph-debuginfo in Hammer was about 0.73GB. > > Having packages that large is problematic on a few fronts: I agree Alfredo. Here's a similar issue I am experiencing with the source sizes: Jewel sizes: 14M ceph-10.2.7.tar.gz 82M ceph-10.2.7 uncompressed Luminous sizes: 142M ceph-12.1.2.tar.gz 709M ceph-12.1.2 uncompressed This adds minutes onto the build times when we must shuffle these large artifacts around: - Upstream we're transferring the artifacts between Jenkins slaves and chacra and download.ceph.com. - Downstream in Fedora/RHEL land we're uploading these source tars to dist-git's lookaside cache, and it takes a while just to upload/download. - Downstream in Debian and Ubuntu (AFAICT) they upload the source tars to Git with git-buildpackage, and this increases the time it takes to even "git clone" these repos. The bundled Boost alone is is 474MB unpacked in 12.1.2. If we could build Boost as a separate package (and not bundle it into ceph) it would make it easier to manage builds upstream and downstream. We could build a boost package in the jenkins.ceph.com infrastructure, or the CentOS Storage SIG (for RHEL-based distros), and then start depending on that system instead of EPEL. For Debian/Ubuntu, we could use jenkins.ceph.com/chacra or something else - any suggestions from Debian/Ubuntu folks? - Ken -- 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
