I am not sure how much they can do upstream, as they are trying to provide one giant tarball of everything a user would need to work from their binary artifact. I think we need to be a bit smarter when we toss the stuff around duing the package build. Right now, we are simply tagging along all the libs and all that crap. Instead we should rely more on what components we are providing as the part of the stack. Say, there's no reason to carry spark junk, because we already have it in the stack, etc.
Makes sense? Cos On Fri, Jan 22, 2016 at 06:11PM, RJ Nowling wrote: > Should we bounce this upstream? > > > On Jan 22, 2016, at 4:33 PM, Konstantin Boudnik (JIRA) <[email protected]> > > wrote: > > > > Konstantin Boudnik created BIGTOP-2269: > > ------------------------------------------ > > > > Summary: Reduce the size of Zeppeling package > > Key: BIGTOP-2269 > > URL: https://issues.apache.org/jira/browse/BIGTOP-2269 > > Project: Bigtop > > Issue Type: Bug > > Components: debian, rpm > > Affects Versions: 1.0.0 > > Reporter: Konstantin Boudnik > > Priority: Blocker > > Fix For: 1.2.0 > > > > > > The size of the package for 0.5.6 is more than 0.5GB. Looks like it does > > package everything it could along the way, and perhaps a few times. This is > > _insane_ and has to be addressed. This monster becomes bigger than the life > > itself. > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.3.4#6332)
signature.asc
Description: Digital signature
