Github user stanlyxiang commented on the issue:

    https://github.com/apache/incubator-hawq/pull/1226
  
    I tested on my rhel7. After build rps rpm, there are 2 commands after the 
rpm generate.
    `
    [INFO] + cd 
/home/xsheng/hawq/incubator-hawq/ranger-plugin/target/rpm/hawq-ranger-plugin/BUILD
    [INFO] + /usr/bin/rm -rf 
/home/xsheng/hawq/incubator-hawq/ranger-plugin/target/rpm/hawq-ranger-plugin/buildroot
    `
    Since previous install method is copying the ranger folder under buildroot, 
but now the content of BuildRoot is deleted automatically on rhel7. Because the 
rpmbuild version is 4.11.3. 
    I searched on the internet and found that the old version of rpmbuild will 
keep the folder and we can copy the files to installdir. But on rhel7 the 
rpmbuild is high version and will remove the buildroot. So the installation 
will fail. 
    
    There are some workarounds I haven't verified because they are required to 
modify the spec file when build rpm. But the spec file for build ranger-plugin 
rpm is generated automatically. 
    
    I checked rpmbuild version on my rhel6 and rhel7. RPM version 4.8.0 and RPM 
version 4.11.3. They all deleted the buildroot folder after build. So there is 
the pr. If you have any solution, please commets. Thanks in advance. 
    
    On my mac the rpm is "rpm (RPM) 5.4.15" and "rpmbuild (RPM) 5.4.15", it 
won't remove "buildroot". I think it's rpm5. 
    
    Concourse ci build and install the ranger-plugin.rpm separately so it's 
green. If we use rpm to install the ranger-plugin during hawq installation, we 
should use "rpm --prefix=/hawq/install/path  ranger-plugin.rpm". But I tried 
and got an error: 
    `rpm: --prefix may only be used when installing new packages`. So it not 
reality for a community user or developer to rpm uninstall and rpm install 
everytime they have changes. 


---
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 and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to