[
https://issues.apache.org/jira/browse/HADOOP-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879263#action_12879263
]
Konstantin Boudnik commented on HADOOP-6255:
--------------------------------------------
It seems like people here are fond of having a separate project from the Hadoop
itself. While it seems like good idea I can see slight different approach. Here
it is:
- native packaging specs (DEBs, RPMs, whatnot) are placed within the current
build systems i.e. under {{$project.root/packaging/specs}}
- existing {{build.xml}} is extended with an extra target {{create-packages}}
depends on perhaps {{tar}}
- an execution of
{{ant create-packages -Dpackage.type=RPM|DEB
-Dpackage.arch=noarch|x32|x64|ARM}}
will exec a package creation script from {{$project.root/packaging/scripts}}
using spec specified by {{package.type}}
- similarly, test packages can be produced by
{{ant create-packages -Dpackage.type=RPM|DEB -Dpackage.class=test}}
IMO this approach should allow for reuse of some of existing build
functionality without adding any extra hassle to the current build system.
Besides, the packaging will be kept as a part of the project itself however
will be physically separated from the build system.
Any dependencies resolvable as packages of certain type needs to be listed as
external dependencies. Non-resolvable (like Avro above) will have to be
included.
bq. We also need to separate the client from the server rpms
+1 on this one.
> 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.
