Bug 1386246 - Provide %license macro for better compatibility between Fedora/RHEL7 and RHEL6
Summary: Provide %license macro for better compatibility between Fedora/RHEL7 and RHEL6
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: scl-utils
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6
Assignee: Joe Orton
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1420233
TreeView+ depends on / blocked
 
Reported: 2016-10-18 13:30 UTC by Vít Ondruch
Modified: 2020-12-15 07:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:47:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1334670 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1386241 0 unspecified CLOSED Document RHEL 6/7 incompatibilities 2021-02-22 00:41:40 UTC

Internal Links: 1334670 1386241

Description Vít Ondruch 2016-10-18 13:30:53 UTC 
Description of problem:
In Fedora and RHEL7, there is possible to mark license files using %license macro. It would be nice to have %license macro available on RHEL 6 as well. 

I met this workaround on one package [1]:

%{!?_licensedir:%global license %%doc}

It would be even better to have this macro on RPM itself, but not sure if that is possible to get this into RHEL, so proposing this for scl-utils, since we had some fun with this during RHSCL 2.3 rebuild of RHEL7 SCLs for RHEL6.




[1] http://pkgs.fedoraproject.org/cgit/rpms/rubygem-pry.git/tree/rubygem-pry.spec#n100
Comment 6 RHEL Program Management 2020-12-15 07:47:14 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.