hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Koch (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-6597) additional source only release tarball
Date Thu, 25 Feb 2010 15:17:28 GMT
additional source only release tarball

                 Key: HADOOP-6597
                 URL: https://issues.apache.org/jira/browse/HADOOP-6597
             Project: Hadoop Common
          Issue Type: Wish
            Reporter: Thomas Koch
            Priority: Trivial

One common annoyance when packaging java applications for a Free Software distribution is
the necessity to repackage the upstream tarball. The repackaging is necessary, because Debian
may only distribute binary files build from source that's also available from Debian.
So we build the jar/war files ourselfes to make sure there's nothing we don't have the sources
It would take one (annoying and time consuming) step less for packagers, if java upstream
projects would release an additional tarball without any binary files or third party code.
I'm asking you first, because many other projects (like zookeeper) took or take hadoop as
an example for their build infrastructure.
For your orientation, these are the patterns that I used to filter the hadoop tarball: (Usable
with tar --exclude)


There were different reasons why stuff needed to be filtered:
- unclear license (uming.*)
- unclear origin (images in the eclipse plugin)
- precompiled documentation / code / hadoop binaries
- pregenerated C/C++ automake files
- third party libraries (prototype.js, lib/*.jar)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message