> For issue #2 I was concerned that the build & packaging had to be > internal. So I am using the already packaged make-distribution.sh > (modified to use a maven build) to create a tar ball which I then package > it using a RPM spec file.
Hi Rahul, so the issue for downstream operating system distributions is that they basically need to be able to build everything from source. So while you're building Spark itself locally, a package that appears in Fedora or Debian will go a bit further and also build all of the library dependencies, compilers, etc., from sources (possibly with some exceptions for bootstrapping compilers that can't be built without themselves) rather than pulling down binaries from a public Maven or Ivy repository. > Although on a side note, it would interesting to learn how the list of > files does not need to be maintained in the spec file (the spec file that > Christophe attached was using a explicit list). If you take a look at the spec that is in Fedora (http://pkgs.fedoraproject.org/cgit/spark.git/tree/spark.spec, starting at line 257 in the current revision), you'll see the following %files section: %files -f .mfiles %dir %{_javadir}/%{name} %doc LICENSE README.md %files javadoc %{_javadocdir}/%{name} %doc LICENSE As you can see, this list is pretty generic (and obviously doesn't include all the files in the package). The list of JAR and POM files is provided in a file called .mfiles (which is automatically generated by macros) and we just have to specify the directories that the package owns (which aren't picked up by the macros at this time), the license, and the README. best, wb
