Bug 1265021
Summary: | RFE: Add %autosetup macro | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Orion Poplawski <orion> | ||||
Component: | rpm | Assignee: | Packaging Maintenance Team <packaging-team-maint> | ||||
Status: | CLOSED ERRATA | QA Contact: | Karel Srot <ksrot> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.7 | CC: | j, lkardos, tlavigne | ||||
Target Milestone: | rc | Keywords: | FutureFeature | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Enhancement | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-05-11 00:54:02 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Orion Poplawski
2015-09-21 22:14:44 UTC
Not sure if we want to backport %autosetup to rhel6 rpm. But %autosetup is not hardcoded in rpm, it is implemented by macros. That means you can easily add %autosetup to your system by adding the content of the attached file into your ~/.rpmmacros or create some file in /etc/rpm and put the content there (then it will be available for all users). Is that acceptable solution for you? Created attachment 1100923 [details]
autosetup_macros extracted from /usr/lib/rpm/macros
The goal is to allow Fedora/EPEL rpms to share the same spec file. If it's not going to be added to RHEL's rpm macros, we can add it to epel-release or similar. We want to have macros like this in one place. Devel ack for adding autosetup macros into rpm package. I was just CC'd on this. epel-rpm-macros has autosetup currently, but if it's going into some base RHEL release then we can remove it. The question is, when should this happen? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0936.html |