[
https://issues.apache.org/jira/browse/HADOOP-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880058#action_12880058
]
Konstantin Boudnik commented on HADOOP-6255:
--------------------------------------------
After a good discussion with Owen and Roman here's the a better proposal:
- new top level targets to be introduced into ant build:
-- package-32
-- package-64
-- package-noarch
-- package depends on all above
It is up to build to find out about the type of OS the build is running on and
either to locate appropriate packaging script and schema or fail with
appropriate diagnostics.
The preliminary structure of installed packages is like this:
{noformat}
$root/
bin/
hadoop
hadoop-daemon?.sh
hdfs
mapred
<other user facing scripts>
share/
hadoop/
bin/
hadoop-config.sh
lib/
*.jar
man/
include/
c++/
sbin/
jvsc
taskcontroller
runAs (for Herriot packages)
{noformat}
Some notes:
- jar files in {{share/hadoop/lib/}} have to have their owners based on the
components they are coming from (e.g. hdfs-client, hdfs-server, etc.)
- packages required by Hadoop but aren't included into its source code (LZO is
a good example) shall be delivered via inter-package dependencies.
Something has to be done about configs. Shall they be placed under
{{/etc/hadoop}} perhaps?
Herriot package (test for real cluster as in HADOOP-6332) shall be created
separately because it requires byte-code instrumentation.
> Create an rpm integration project
> ---------------------------------
>
> Key: HADOOP-6255
> URL: https://issues.apache.org/jira/browse/HADOOP-6255
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Owen O'Malley
>
> We should be able to create RPMs for Hadoop releases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
