[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-27 Thread radarwave
Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 This PR is for build HAWQ rpm from binary tarball, since now we chose using source tarball to build rpm packages, so open another PR for the review. New PR link is:

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-20 Thread kdunn926
Github user kdunn926 commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 +1 to @paul-guo- 's approach. One spec file to rule them all. Will be more maintainable. --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-20 Thread paul-guo-
Github user paul-guo- commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 If I understand correctly, we seem to make things a bit complicated. Why not generate a src.rpm and rpm based on source tarball + one spec file directly? Below is an example from

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-17 Thread radarwave
Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 @edespino I think this is only for open source release. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-17 Thread radarwave
Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 @edespino A jira is created to trace build rpm package from source tarball, this time we will focus on rpm build from binary tarball. See:

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-17 Thread edespino
Github user edespino commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 @radarwave - to keep things moving along for the upcoming Apache HAWQ 2.2.0.0-incubating release, I suggest you open a Jira to address building from source tarball in the spec file and

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-17 Thread edespino
Github user edespino commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 @radarwave - As soon as this is committed, this should be the only spec file used to generate HAWQ rpms for both Open Source or commercial releases. Is this a true statement? --- If

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-17 Thread radarwave
Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 @edespino Good point to build HAWQ rpm from source tarball. We should be able to build a rpm package by both pre-build binary tarball and source tarball. --- If your project is set up

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-17 Thread edespino
Github user edespino commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 As a general spec file to produce a pre-built binary releaes of HAWQ, this is a good starting point. Ideally, the spec file will also have a "build" section which is used to build the

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-16 Thread xunzhang
Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 @radarwave TIL, thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[GitHub] incubator-hawq issue #1177: HAWQ-326. Support RPM package for Apache HAWQ.

2017-03-16 Thread radarwave
Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/1177 @xunzhang I guess you are doing some package works on many systems. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If