Hi, I am currently learning the ins and outs of bigtop to work on the Cascading integration (https://issues.apache.org/jira/browse/BIGTOP-1766). I have a few questions around packaging in bigtop:
1) most linux distros have packaging guidelines that should be followed. Does bigtop follow any set of rules in particular? Is there a linting tool for spec files etc? 2) Related to 1): Does bigtop require to follow a certain directory layout? Our tools are currently meant to be untarred and used as is, if bigtop requires them to be split over the file-system, we will have to work on that upstream before they can be included. 3) I noticed that the packages are build from source instead of re-using binary releases. Is that a strict requirement or does it just happen to be that way? For the Cascading integration I was planning on downloading our binary releases so that bigtop ship with the same bits as our SDK. 4) What is your take on packaging standalone libraries? I noticed that most parts of bigtop are tools in the broader sense. Something one can invoke on the command line, but there is also a package for apache crunch, which is a library. What is the reasoning here? Would it make sense to build packages for libraries in the Cascading eco-system? Thanks for your answers! - André -- André Kelpe [email protected] http://concurrentinc.com
