Bug 731279
Summary: | gem2rpm spec file default template generates spec files incompatible with epel | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Oded Arbel <oded> |
Component: | rubygem-gem2rpm | Assignee: | Vít Ondruch <vondruch> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | mastahnke, vondruch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-23 06:56:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Oded Arbel
2011-08-17 09:03:31 UTC
I found that the fedora template works mostly fine to build gems, so I just copied it to epel.spec.erb and added this to distro.rb: elsif !release_files.grep(/redhat/).empty? EPEL (this also works for CentOS 6 as that also has a /etc/redhat-release file) Hi, As you already found, the "default.spec.erb" template is used if the distribution is not recognized, which is the case of EPEL. However, you can always use the "--template TEMPLATE" to specify your very own template without need of patching gem2rpm. I would like to accept the change you have proposed, but I am bit reluctant, because I am not using EPEL personally and this template would need some maintainer. Would you volunteer for maintaining the EPEL template? Other solution is to use the "fedora.spec.erb" template also for EPEL, i.e. to change [1] into form: if !release_files.grep(/fedora|redhat/).empty? [1] https://github.com/lutter/gem2rpm/blob/master/lib/gem2rpm/distro.rb#L8 Thanks for the reply. Initially I used the fedora template, but found that it is also missing some things (such as requiring gcc when building GEMs with native extensions). I'm willing to maintain an EPEL specific template, or if its possible to fix the Fedora template to work for EPEL that would also work nicely - though I'm not using Fedora with GEMs, so I have no way to test how suggested changes affect Fedora. May be the best would be if you can send a pull request on github with your proposed changes? Or show me the template you used for EPEL ... Please open PR on GitHub if you are still interested. I'm closing this issue. Thank you. |