No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
== Rationale == | == Rationale == | ||
Update guidelines to | Update guidelines to support and recommend %make_install over the expanded definition. It is simpler to use and would be convenient for new packages. The expanded should continue to be supported but deprecated so that old spec files can be incrementally switched over. | ||
Revision as of 17:42, 4 June 2012
It is still under construction and content may change. Do not rely on the information on this page.
Rationale
Update guidelines to support and recommend %make_install over the expanded definition. It is simpler to use and would be convenient for new packages. The expanded should continue to be supported but deprecated so that old spec files can be incrementally switched over.
Using %make_install
%make_install is defined at http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=883253ea6af71f8063d7a045841c35bad22147e2 and available since RPM 4.8. The current packaging guidelines use the expanded make install DESTDIR=%{?buildroot} before the make_install macro was added to upstream RPM. We should modify the packaging guidelines to suggest using the macro in place of the full definition. The alternative should continue to be acceptable since mass conversion isn't necessary. The recommendation would mostly apply for new packages.
Note: %makeinstall is bad and wrong and is only left in upstream RPM for compatibility. %make_install is the new and recommmended method.