[
https://issues.apache.org/jira/browse/HADOOP-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880359#action_12880359
]
Roman Shaposhnik commented on HADOOP-6255:
------------------------------------------
I have two points to add to the discussion:
1. I'm wondering whether it would be useful to slice it a bit more thinly.
IOW, introducing the notion of these extra
top level targets available for packaging:
hadoop-core
hadoop-client
hadoop-daemon
hadoop-devel
hadoop-javadoc
2. As for configs, I'd like to point out an example that Debian has
established with their packaging of .20. Basically
they created one package per node type
(http://packages.qa.debian.org/h/hadoop.html) plus one package common
among all the daemons:
hadoop-daemons-common
hadoop-jobtrackerd
hadoop-tasktrackerd
hadoop-datanoded
hadoop-namenoded
hadoop-secondarynamenoded
The packages themselves are pretty slim -- containing only hooks to
make daemons plug into the service management
system (init.d in Debian's case, but one would imagine Solaris/SMF or
anything like that also being an option for us).
I also would tend to believe that these could be reasonable packages
to be used for splitting the configs appropriately.
> 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.
