Changes between Version 7 and Version 8 of RpmHowToPackagers
- Timestamp:
- Sep 10, 2010, 12:44:10 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RpmHowToPackagers
v7 v8 26 26 27 27 == Prepare source code == 28 This is done in the ''%prep'' section. Here the ''%setup'' macro will expand your source package (the one in the ''Source:'' line) and write the files by default in the %HOME%\rpmbuild\BUILD\{name}- 29 {version} directory. You can change this with ''-n'' parameter for %setup macro. 28 This is done in the ''%prep'' section. Here the ''%setup'' macro will expand your source package (the one in the ''Source:'' line) and write the files by default in the %HOME%\rpmbuild\BUILD\{name}-{version} directory. You can change this with ''-n'' parameter for %setup macro. 30 29 31 30 If you need to extract more source files, use the ''-a'' parameter. … … 40 39 %patch001 -p1 -b .base 41 40 }}} 41 Note that rpmbuild defaults expectes to find source tarball and patches in the SOURCES directory. 42 42 43 43 == Build source code == … … 102 102 103 103 All output files will be written in the %HOME%\rpmbuild tree, regardless of current directory and drive. 104 105 == OS/2 specific notes == 106 While the syntax of .spec files is the same used under Unix, not everything is currently working in the OS/2 port. Also many packages are already built and manually installed: this means RPM is not aware of their presence. 107 108 Many Unix .spec files have a (or multiple) ''BuildRequire:'' rules: if the package is not already built with RPM, the line should be commented until the required package will have a RPM install. The same applies to ''Requires:'' rules. 109 110 Another missing feature is the automatic detection of required DLLs or packages: Unix rpm does this analyzing the ELF binaries and adding the required DLLs on the fly; the same is done for python or perl scripts, the required abi level is added by parsing scripts and querying python/perl modules.[[BR]] 111 Under OS/2 these requirements must be manually added using a ''BuildRequires'' or ''Requires'' rule. 112 Example: 113 {{{ 114 Requires: python 115 Requires: python(abi) = 2.6 116 }}} 117