Churchyard (talk | contribs) mNo edit summary |
Churchyard (talk | contribs) mNo edit summary |
||
Line 7: | Line 7: | ||
| All Fedoras || 1 || 1 || 0 || 1 | | All Fedoras || 1 || 1 || 0 || 1 | ||
|- | |- | ||
| EPEL 7 || 0 || 1 || | | EPEL 7 || 0 || 1 || 0 || 1 | ||
|- | |- | ||
| EPEL 6 || 0 || 1 || | | EPEL 6 || 0 || 1 || 0 || 1 | ||
|} | |} | ||
It's up to the packager whether they conditionalize on the <code>must</code> or <code>may</code> macros, or whether they use those macros at all. | It's up to the packager whether they conditionalize on the <code>must</code> or <code>may</code> macros, or whether they use those macros at all. |
Revision as of 17:40, 1 March 2018
For packagers who like to share a common spec file between Fedora and EPELs, the following macros are defined in EPEL and Fedora that you can use in conditionals. For each Python runtime, there are 2 versions of the macros: a must
version (that says whether the packager must package for that runtime if possible) and a may
version (that says that if the packager wants to, they may package for that runtime). Note that even if some macro currently expands to 1 an all Fedoras and EPELs, it maight change in the future.
%py3_must |
%py3_may |
%py2_must |
%py2_may
| |
---|---|---|---|---|
All Fedoras | 1 | 1 | 0 | 1 |
EPEL 7 | 0 | 1 | 0 | 1 |
EPEL 6 | 0 | 1 | 0 | 1 |
It's up to the packager whether they conditionalize on the must
or may
macros, or whether they use those macros at all.